-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 9
-
Component/s: core-libs
-
None
-
b71
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8136294 | emb-9 | Attila Szegedi | P4 | Resolved | Fixed | team |
| JDK-8131009 | 8u65 | Attila Szegedi | P4 | Resolved | Fixed | b05 |
| JDK-8129856 | 8u60 | Attila Szegedi | P4 | Resolved | Fixed | b22 |
| JDK-8138557 | emb-8u65 | Unassigned | P4 | Resolved | Fixed | b05 |
| JDK-8130617 | emb-8u60 | Attila Szegedi | P4 | Resolved | Fixed | b22 |
If a class has a variable arity constructor, e.g. VarArgClass(String... x), and we create a class-level Java adapter for it using Java.extend(VarArgClass, { ... }), the variable constructor in the adapter should also be variable arity.
We lose variable arity constructors for adapters with instance-level overrides as we need to pass an extra trailing argument in the constructor, but there's no reason to lose them for class-level overrides.
We lose variable arity constructors for adapters with instance-level overrides as we need to pass an extra trailing argument in the constructor, but there's no reason to lose them for class-level overrides.
- backported by
-
JDK-8129856 Java adapters with class-level overrides should preserve variable arity constructors
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-