it worked for me. I didn't see any errors on loom scopes or the panama
API. I also remember testing the RNG package years ago (not 100% sure if
it was an incubating API).
You have to make sure that NB is using the right javac, and that the
delta of the ea JDK and the actually supported javac isn't too large. I
don't think testing JDK 19 with nb 12.6 will work (asm would probably
already fail), but rudimentary tests showed NB 13 should do fine.
Its rather the opposite. If nb doesn't know a language feature yet, the
editor might break in various ways - nobody can look into the future and
implement it in present. APIs are more likely to work.
In general running NB with javac n+1 should work ok for experiments if
you use the javac of the ea jdk.
-mbien
On 01.02.22 07:22, Ty Young wrote:
Thanks for bringing this up.
--enable-preview generally worked just fine in the past with
*language* features. This, being an API preview, seems to be different.
On 1/31/22 7:18 AM, Scott Palmer wrote:
Just FYI…
https://mail.openjdk.java.net/pipermail/panama-dev/2022-January/016137.html
I don’t recall having issues when --enable-preview was required in
the past, but I could be mis-remembering.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
