-
Bug
-
Resolution: Fixed
-
P3
-
8
-
b08
-
Verified
- asMemberOf
- capture
- directSupertypes
- erasure
- getArrayType
- getDeclaredType x2
- getWildcardType
- unboxedType
Per [1], it is desirable to ensure that no type annotations appear in the returned TypeMirror objects (when viewed as AnnotatedConstruct objects). jx.l.m.u.Types should say: "Utility methods for operating on types. Where a method returns a TypeMirror, the TypeMirror represents a type with no type annotations."
[1] http://mail.openjdk.java.net/pipermail/compiler-dev/2014-May/008756.html
- csr for
-
JDK-8323620 Strip type annotations in Types' utility methods
-
- Closed
-
- duplicates
-
JDK-8281235 com.sun.tools.javac.code.Types.erasure inconsistently removes annotations
-
- Closed
-
- relates to
-
JDK-8055219 Handling of non-standard inputs in javax.lang.model.util.Types
-
- Open
-
-
JDK-8323684 TypeMirror.{getAnnotationsByType, getAnnotation} return uninformative results
-
- Resolved
-
-
JDK-8324786 validate-source fails after JDK-8042981
-
- Closed
-
-
JDK-8031744 Annotations on many Language Model elements are not returned
-
- Closed
-
-
JDK-8291643 Consider omitting type annotations from type error diagnostics
-
- Resolved
-
-
JDK-8281235 com.sun.tools.javac.code.Types.erasure inconsistently removes annotations
-
- Closed
-
-
JDK-8174126 Add Types method to add annotations
-
- Open
-
- links to
-
Commit openjdk/jdk/ed3272cc
-
Review openjdk/jdk/8984
-
Review(master) openjdk/jdk/8984