[foreign] RFR 8218153: Read/Write of Value layout should honor declared endianness

[John Rose]

I would be very happy with this outcome, and I think we can also
make the users happy (in their various kinds and factions),
by providing a tidy menu of import options.

On Jan 31, 2019, at 10:59 AM, Maurizio Cimadamore <maurizio.cimadamore at oracle.com> wrote:
> 
> I think all this goes for the nuclear option (c), with some static import reliefs.
> 
> I also think that inferring LE or BE always (as per my option b) is as wrong as inferring platform endianness - in terms of place where bugs can hide, and difficulty in terms of finding where such bugs are coming from (because it's implicit).
> 
> So, I think the Value layout API should NOT have a default constructor w/o endianness.
> 
>