JEP proposed to target JDK 11: 323: Local-Variable Syntax for Lambda Parameters
benjamin.john.evans at gmail.com
Fri Jan 26 09:26:37 UTC 2018
This is a riff on an unreleased feature.
We do not have any data on how LVTI will actually be used by the Java
community in the field yet.
It may prove to be wildly popular, or it may not. We simply don't know yet.
Therefore, why are we rushing to build on top of it as part of the
very next release?
If LVTI turns out to be hugely popular, there will be another release
along in 6 (or 12) months time where we can implement this.
But why now? Why rush, in advance of seeing how our users will
actually use the bedrock feature on which this rests?
Java already has, IMO, far too much syntactic cruft and edge cases,
much of it from the early days. It can never be fixed, and we all just
have to live with it.
Why rush to add unproven features that may just add more syntax that
needs to be worked around?
On Thu, Jan 25, 2018 at 8:40 PM, <mark.reinhold at oracle.com> wrote:
> The following JEP is proposed to target JDK 11:
> 323: Local-Variable Syntax for Lambda Parameters
> Feedback on this proposal is more than welcome, as are reasoned
> objections. If no such objections are raised by 23:00 UTC on Thursday,
> 1 February, or if they're raised and then satisfactorily answered, then
> per the JEP 2.0 process proposal  I'll target this JEP to JDK 11.
> - Mark
>  http://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html
More information about the jdk-dev