This table summarizes what known open issues are, both in the specification and the RI, and points to the discussions on the mailing lists.
|Issue||Next responsible||Email thread|
|Desugaring of anonymous classes||EG, Steve|
Finalize the discussion:
Ensure the implementation is in conformance.
|Receiver parameter name||EG, wmdietl|
Receiver parameter name checks should not be based on Strings, but on semantics:
The EG needs to finalize the spec on what receiver parameter names are legal:
|Receiver parameter API||wmdietl|
Provide nicer integration of receiver parameters:
|Method/Constructor distinction||EG||A proposed change needs to be decided:|
|Interaction between Target and qualified names||wmdietl|
Ensure recent discussion is implemented:
|JLS Creator production||EG, Mike|
A production needs an update in the spec:
|Review multi-catch implementation||Jon, Vicente|
|Cleanup test cases||Joel, Steve|
|Address remaining javadoc issues (type annos on type parameters)||Jon, Bhavesh||See @ignored test cases in javadoc type anno tests|
wmdietl will also keep the Google Code issue tracker up-to-date:
Aspects that should be tested more thoroughly by SQE:
- target information for type annotations in anonymous classes and lambdas
- bytecode offset for local variables, cast, instanceof, etc.
- receiver parameter types and names
- access to annotated types (expand test/tools/javac/processing/model/type/BasicAnnoTests.java)