-
Bug
-
Resolution: Fixed
-
P4
-
9
-
None
-
b103
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8149327 | 8u101 | Hannes Wallnoefer | P4 | Resolved | Fixed | b01 |
| JDK-8148070 | 8u92 | Hannes Wallnoefer | P4 | Resolved | Fixed | b04 |
| JDK-8155512 | emb-8u101 | Hannes Wallnoefer | P4 | Resolved | Fixed | b01 |
The varargs methods of the Array unshift() and push() methods can still return longs, which shouldn't be the case after JDK-8143896 as longs are no longer considered JavaScript Numbers. This normally only occurs with optimistic types disabled.
var x = [1, 2, 3];
print(x.push() === 3); // prints false instead of true
print(x.unshift() === 3); // prints false instead of true
var x = [1, 2, 3];
print(x.push() === 3); // prints false instead of true
print(x.unshift() === 3); // prints false instead of true
- backported by
-
JDK-8148070 Varargs Array functions still leaking longs
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-