On 04.11.2016 00:32, mark.reinh...@oracle.com wrote:
2016/11/1 14:17:43 -0700, neil.bartl...@paremus.com:
...
In scenarios where a module's author
can't foresee the need for such access (e.g., intrusive serialization
frameworks) then the framework's author must take more drastic measures
(e.g., use the legacy unsupported unsafe API). This balance is intended
to help maintain the integrity of a module as expressed by its author.
Since Unsafe was mentioned here... All the ways I did know to get to
Unsafe required reflection on private members. Afaik
#AwkwardStrongEncapsulation will block that. So how can I still use
Unsafe in the future or did it get some "proper" public way to get hold
of an Unsafe by now and I missed that?
bye Jochen
