We could use a multi-release jar to still provide a faster option for pre
jdk9 users but avoiding that added complexity would also be a good thing.
On Sat, Oct 14, 2017 at 12:28 AM, John Wagenleitner <
john.wagenleit...@gmail.com> wrote:
> I would be in favor of removing Unsafe from the groovy-j
I would be in favor of removing Unsafe from the groovy-json subproject
which I think is the only place where it's used. I had planned to propose
this to the dev list but never got around to it. With compat strings in
Java 9 I believe it will no longer be a viable optimization (at least not
without
Am 13.10.2017 um 10:47 schrieb Jochen Theodorou:
Am 13.10.2017 um 09:52 schrieb Uwe Schindler:
FYI,
getting Unsafe does not print a warning, as reflection is "open" on
the jdk.unsupported module. This was decided in JEP 260.
ups, yes, sorry, forgot that.
and of course while true for Uns
Am 13.10.2017 um 09:52 schrieb Uwe Schindler:
FYI,
getting Unsafe does not print a warning, as reflection is "open" on the
jdk.unsupported module. This was decided in JEP 260.
ups, yes, sorry, forgot that.
Uwe
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de
eMail
FYI,
getting Unsafe does not print a warning, as reflection is "open" on the
jdk.unsupported module. This was decided in JEP 260.
Uwe
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Jochen Theodorou [mailto:b
