Bug in javac and eclipse ??

Markus Keller markus_keller at ch.ibm.com
Wed Jan 22 03:09:20 PST 2014


Remi, you are totally correct, this is a spec bug (oversight, since 8.3.3 
was not updated when lambdas were added).
The Eclipse compiler had this right, until we bowed down to the bad spec: 
https://bugs.eclipse.org/421926

Unfortunately, my first mail on this subject was not perfect, since I 
first also thought this was about "Self-reference to field from lambda 
expression in initializer". Dan's answer also referred to a "recursive 
lambda expression" feature, which shows that Oracle's internal discussion 
was also based on wrong assumptions.

Here's the revised spec fix request, but unfortunately, this new request 
was rejected from the lambda-spec-comments list:
http://mail.openjdk.java.net/pipermail/lambda-spec-observers/2013-December/000623.html

> REQUEST:
> ========
> 8.3.3 should get a fifth point:
> "- The usage is not in a lambda expression body that occurs inside c."

Remi and other EG members, please fix this.

Thanks,
Markus



More information about the lambda-spec-observers mailing list