[foreign-memaccess+abi] RFR: 8291473: Unify MemorySegment and MemoryAddress [v5]

[Radoslaw Smogura]

On Thu, 28 Jul 2022 17:18:04 GMT, Maurizio Cimadamore <mcimadamore at openjdk.org> wrote:

>> src/java.base/share/classes/java/lang/foreign/MemorySegment.java line 261:
>> 
>>> 259:      * {@return the Java array associated with this memory segment, if any}
>>> 260:      */
>>> 261:     Optional<Object> array();
>> 
>> I wonder if array word is not too strict, I think what if we would use value object as a base for struct (sometime in future).
>
>> I wonder if array word is not too strict, I think what if we would use value object as a base for struct (sometime in future).
> 
> I think you are correct, the word might indeed be too strict. "Heap container" is what we're after, but I'm not sure if having a method named "heapContainer" would fly?

I'm not good at finding names. I got used to `base`. Maybe heapBase or heapObject. I'll think about it and come back if I invite something worth of mentioning.

-------------

PR: https://git.openjdk.org/panama-foreign/pull/694