identityless objects and the type hierarchy

[Kevin Bourrillion]

On Wed, Nov 3, 2021 at 12:43 PM Brian Goetz <brian.goetz at oracle.com> wrote:

>
> On 11/3/2021 3:00 PM, Kevin Bourrillion wrote:
>
> Okay, let's stick a pin in proper-value-types (i.e. try to leave them out
> of this discussion) for a moment...
>
> One question is whether the existing design for the bifurcated type
> hierarchy will carry right over to this split instead.
>
> Brian, your response reads like it is explaining/defending *that* design
to me. But I believe I already understood it and wasn't expressing any
problem with it.

Now we're talking about making a smaller split first, "identity objects vs.
identityless objects" (1 vs 2, not 1 vs 3), so I was inquiring into why
that class model does or does not also work exactly as-is for *this *
purpose.

(Note that I assume if bucket 3's arrival requires another such type in the
mix, there would be a second such bifurcation under IdentitylessObject.)

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