Bug in javac and eclipse ??
daniel.smith at oracle.com
Wed Jan 22 09:39:21 PST 2014
On Jan 22, 2014, at 4:09 AM, Markus Keller <markus_keller at ch.ibm.com> wrote:
> 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:
> 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.
Can you clarify what incorrect assumptions you think were made? I'm not seeing any new information in this thread.
I've tried to be very clear about where were at: sure, it would be convenient to do something here, but it's a complicated space and it deserves a lot more analysis before we commit to something. It's at the top of our "potential future enhancements" list.
More information about the lambda-spec-experts