[External] : Re: Consolidating the user model

[Kevin Bourrillion]

On Thu, Nov 4, 2021 at 7:56 AM Brian Goetz <brian.goetz at oracle.com> wrote:

On 11/4/2021 2:54 AM, Kevin Bourrillion wrote:
>
> Point.ref pr = pv;  // same object… now it’s on the heap, though, with a
>> real live heap header
>> assert pr.getClass() == Point.class;  // same class, but...
>>
>
> Why would we even want this? It would be very surprising/puzzling to me.
>
> It's surprising because we're so used to "boxes" being a thing.  But let's
> look at this a bit.
>

Okay, it's clear I have more work to do in understanding your whole
coherent model as it exists.

Summary of what kevinb has been on about the last 24 hours:

The model I've been speaking for over the past day has flowed from
following my own "I want to think it's as simple as...." intuitions. I
expected to sort of "hit a wall" with those naive assumptions and never
felt like I did (yet).

Your model is likely enough the best, and I'm simply "resisting" it, but in
that case I'm channeling some of the resistance other users will feel, and
we can hash out how to head it off. But also, occasionally I turn out to be
right about things so I'll prepare for that misfortune as well.

I think it's worth my understanding both models until I can explain them
well, and *then* we can make more progress. Let's just name the models.
Fair enough? (Feel free to inject "no need to name your model because I can
give the killer argument right now why it just can't work", I mean we
wouldn't name a woodland animal we found moments from death on the side of
the road, would we.)

--
Kevin Bourrillion | Java Librarian | Google, Inc. | kevinb at google.com