Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jdt-dev] Incubating Java Language Features

Thanks Mike.

I believe, some of these were already happening already as part of the openjdk development process. But just as in the past, the "impermanent" nature of these feature is definitely a concern for us, the JDT team. What makes it a bigger concern is this, (based on my understanding, of course):

The compilers and runtimes should support these incubating features, although they are turned off by default. This basically means every compiler implementation should evolve simultaneously with respect to the incubating features. But at the same time, not all of them are certain to be a permanent feature.

Even if the above is not true, it is going to be a challenge to decide our own plan based on the direction the incubating feature is going to take. Are we to build these features even as the discussions happen or are we to wait for these to become permanent and start on our implementation.

Either way, it's going to be quite a challenge!

Regards,
Jay






From:        Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx>
To:        jdt-dev@xxxxxxxxxxx
Cc:        eclipse-pmc@xxxxxxxxxxx, Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
Date:        01/30/2018 04:42 PM
Subject:        [jdt-dev] Incubating Java Language Features
Sent by:        jdt-dev-bounces@xxxxxxxxxxx




All,

Just in case you've missed it, I would like to draw your attention to a recent proposal on the jdk-dev list entitled "Incubating Language and VM Features". The conversation on the mailing list starts here. At its core, I *think* this means that staying abreast of new language features will require engaging with OpenJDK rather than JSRs hosted at the JCP.

Important quote:

The Umbrella JSR for the Java SE $N Platform enumerates the incubating language and VM features in the platform. The desire for feedback and the expectation of quality means that these features are not "optional"; they must all be supported in full by every implementation of the Umbrella JSR. They are specified in appendices of the Java SE $N Editions of the Java Language Specification (JLS) and the Java Virtual Machine Specification (JVMS). The Java Compatibility Kit for Java SE $N checks conformance of an implementation's incubating features to the appropriate appendix.

If you have any thoughts or concerns about how this may impact ecj or JDT in general, please comment on the jdk-dev mailing list. If there is anything I or the EMO can assist with, please let me know.

Thanks.

--
Mike Milinkovich

mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx
(m) +1.613.220.3223
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_jdt-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=LuMqcl3PU0i2olgTvkVvFthzqyc_3wGfGooplpAvFsc&m=otdJCIXdD0isszl9Nw7AI23ITDJ1H7iQIG4Itm-Yfbw&s=00Xfl2GDFAWNS2yoDEtVCTH_ufnc2-va4Pz-8EJmO30&e=



Back to the top