-
Bug
-
Resolution: Unresolved
-
P4
-
None
javac's treatment of capture is often inconsistent with the specification. Sometimes capture occurs in places other than where it is specified. Sometimes a capture variable is "widened" to its upper bound.
The changes necessary to match the specification seem to run pretty deep; there doesn't seem to be an easy quick fix.
There may be some value in javac's behavior; if so, it should be identified and pushed back into the specification.
The changes necessary to match the specification seem to run pretty deep; there doesn't seem to be an easy quick fix.
There may be some value in javac's behavior; if so, it should be identified and pushed back into the specification.
- relates to
-
JDK-8013843 15.10.3: Array access for array-bounded capture variable
-
- Open
-
-
JDK-7045341 Left subtyping argument must be captured
-
- Open
-
-
JDK-8012039 enum type variable not within its bound
-
- Open
-
-
JDK-8223553 Fix code constructs that do not compile with the Eclipse Java Compiler
-
- Resolved
-
-
JDK-8144123 Invalid code is compiled by Java without error
-
- Closed
-