JDK-6992698 : JSR 292: remove support for transient syntax in polymorphic signature calls
  • Type: Bug
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: unknown
  • Submitted: 2010-10-18
  • Updated: 2011-03-08
  • Resolved: 2011-03-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.
JDK 7
7 b128Fixed
Related Reports
Relates :  
JDK-7012406 - JSR 292: target typing cast and parenthesis
Relates :  
JDK-6981791 - remove experimental code for JSR 292
Relates :  
JDK-6979327 - method handle invocation should use casts instead of type parameters to specify return type
Relates :  
JDK-7010194 - several langtools regression failures after JSR 292 changes (b123)
Description
The initial version if compiler changes supporting 292 features contained special syntax for denoting return type in a polymorphic signature call. Such syntax, leveraging explicit type-arguments in method calls, has been dropped in favor of a syntax leveraging cast:

BEFORE:

s = mh.<String>invokeExact("daddy",'d','n');

AFTER:

s = (String)mh.invokeExact("bunny",'n','d');

Old syntax is still allowed in order to favor migration of existing 292 clients to the new syntax - however, such support is meant to be transient and, consequently, is to be removed.
Comments
SUGGESTED FIX A webrev of this fix is available at the following URL: http://hg.openjdk.java.net/jdk7/tl/langtools/rev/2d5aff89aaa3
14-01-2011
EVALUATION Will fix.
14-01-2011