Yes, but until all the "safe" replacements are in place and vetted (e.g. performance is on par with Unsafe, same functionality is available, etc), I don't see the point of making it even more annoying to grab hold of. The people who are using it will continue using it until the replacements are available, and this is just going to annoy them. Personally, I'd keep it at javac complaining about its use during compilation, and only add additional flag/burden once you're ready for people to move away from it entirely.
On Tue, Jun 23, 2015 at 11:32 AM, <[email protected]> wrote: > 2015/6/23 7:33 -0700, [email protected]: > > Yup, I've seen that but that depends on a few JEPs and large undertakings > > that aren't part of java 9 release, AFAIK. > > Some are, but some aren't. > > It will be possible to continue using sun.misc.Unsafe in JDK 9, but to > do so you'll have to use a new command-line flag, or the reflection API, > and (as always) such usage is unsupported and at your own risk. > > - Mark >
