-
Enhancement
-
Resolution: Fixed
-
P3
-
6
-
generic
-
generic
This RFE tracks all such issues. Please either add a new
description note or link to related issues.
From jplan entry 403:
For an invalid cast, javac will write something like:
Cast.java:1: inconvertible types
found : java.lang.Number
required: java.lang.String
See also: http://blogs.sun.com/ahe?entry=diagnosing_captured_wildcards
Object o = null;
o -= null;
Gives:
Test.java:12: operator - cannot be applied to java.lang.Object,<nulltype>
o -= null;
^
This should be improved. This should not refer to the operator -, but
the operator -=. Furthermore, "java.lang.Object,<nulltype>" is not very
helpful and we should have separate error messages for unary and binary
operators.
- relates to
-
JDK-4881267 improve diagnostic for "instanceof T" for type parameter T
-
- Closed
-
-
JDK-6722234 javac diagnostics need better integration with the type-system
-
- Closed
-
-
JDK-4881269 improve diagnostic for ill-formed tokens
-
- Closed
-
-
JDK-6723516 Confusing generic requirements.
-
- Closed
-
-
JDK-6231440 Better diagnostic desired for common mistake with array creation
-
- Open
-
-
JDK-5101303 misleading "incompatible types" compiler error
-
- Resolved
-
-
JDK-6720185 DiagnosticFormatter refactoring
-
- Closed
-
-
JDK-6730423 Diagnostic formatter should be an instance field of JCDiagnostic
-
- Closed
-
-
JDK-6799605 Basic/Raw formatters should use type/symbol printer instead of toString()
-
- Closed
-
-
JDK-5088624 cannot find symbol message should be more intelligent
-
- Closed
-
-
JDK-6717241 some diagnostic argument is prematurely converted into a String object
-
- Closed
-