-
Type:
Sub-task
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 8
-
Component/s: specification
As part of JEP 213, we'd like to relax the restriction that "If the class instance creation expression ends in a class body ... [and] TypeArgumentsOrDiamond is present after the Identifier, and denotes <>, then a compile-time error occurs."
Instead, this should be allowed in general, but we must check after inference that the inferred type arguments can be expressed in the generated class file's Signature attribute. (I.e., no capture variables, no intersections, etc.)
Instead, this should be allowed in general, but we must check after inference that the inferred type arguments can be expressed in the generated class file's Signature attribute. (I.e., no capture variables, no intersections, etc.)
- relates to
-
JDK-8075896 18: Generalize capture ivars to support diamond anonymous classes
-
- Open
-
-
-
- Closed
-
-
-
- Closed
-
-
JDK-8061650 15.12.2.5: Most specific for generic class constructors different than treatment of methods
-
- Open
-