JDK-8156868 : MethodHandles.zero(Class) doc issues
- Type: Sub-task
- Component: core-libs
- Sub-Component: java.lang.invoke
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2016-05-12
- Updated: 2016-06-09
- Resolved: 2016-06-02
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 9 |
|---|
9 b122Fixed  |
Description
It would be good (but not necessary!) to disclose the meaning of 'default value'. It is not necessary because there is a link to 'empty(...)' method so user could understand that default value is zero/null/void. It would be good to use link in the reference "empty(methodType(type))" and "explicitCastArguments(constant(Object.class, null), methodType(type))" because it's much more easy to access them using link.