[foreign-memaccess] RFR 8224993: Add Unsafe support for MemoryAddress (again)

[Jorn Vernee]

Thanks, I understood it so far. But, I was wondering if new APIs should 
be added to sun.misc.Unsafe as well. sun.misc.Unsafe didn't for instance 
get the rename from get/setObjectXXX to get/setReferenceXXX either.

 From what I understood, sun.misc.Unsafe is only there to allow code that 
relied on it previously to keep working under Java 9+, since there is 
currently no public alternative for some of the functionality. But, in 
general we'd want to discourage use of sun.misc.Unsafe since it's an 
internal API.

Jorn

Maurizio Cimadamore schreef op 2019-05-30 19:12:
> My understanding is that sun.misc.Unsafe is available via the
> jdk.unsupported module - which people can rely upon when writing
> modular code. The jdk.internal Unsafe is just not exported, so you
> will have to burst through module boundary checks in order to access
> it from outside the JDK.
> 
> Maurizio
> 
> On 30/05/2019 17:09, Jorn Vernee wrote:
>> I wanted to ask about the addition of the APIs to sun.misc.Unsafe last 
>> time, but got side-tracked by the test build error and then forgot :/. 
>> I had assumed sun.misc.Unsafe would not be updated going forward? 
>> What's the policy on this?