JDK-8005243 : Restructure method check code to allow pluggable checkers
- Type: Sub-task
- Component: tools
- Sub-Component: javac
- Affected Version: 8
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2012-12-19
- Updated: 2013-06-07
- Resolved: 2013-01-08
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 8 |
|---|
8 b73Fixed  |
Description
The code for performing a method check (Resolve.checkRawArgumentsAcceptable) is fairly monolithic. It's the only method check routine used within javac which means there's no way to plug in an alternate method check routine into the current overload resolution infrastructure. Yet, there are situation in which such a capability would b very useful (see structural most specific check implementation as per lambda EDR 6.0).