JDK-8019646 : Clarify javadoc contract of LambdaMetafactory methods
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang.invoke
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2013-07-02
  • Updated: 2017-05-17
  • Resolved: 2013-10-24
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.
JDK 8
8 b115Fixed
Related Reports
Blocks :  
JDK-8019635 - Use MethodType for LambdaMetafactory contract rather than MethodHandle
Blocks :  
JDK-8015236 - Provide Class.isFuntionalInterface functionality in core reflection
Relates :  
JDK-8008365 - LambdaMetafactory javadoc warnings
Relates :  
JDK-8024138 - (Spec clarification) Lambda Metafactory spec should state DMH constraint on implMethod
Relates :  
JDK-8019225 - typo in LambdaMetafactory.altMetaFactory
Description
Some implementation details of the metafactory are, by design, left unspecified.  But many aspects of the contract -- what inputs are acceptable, how the flags are used, constraints on the result, etc. -- are intended to be consistent across implementations, and should be more precisely specified.
Comments
Note that this is a documentation-only bug. No change in behavior is anticipated.
15-10-2013
Related to JDK-8010828, which could possibly be regarded as a dup of this.
08-09-2013
Need to settle on the types of the arguments, per JDK-8019635, before we can address the informal contract associated with them.
02-07-2013