On Wed, Jul 13, 2022 at 1:24 PM John Rose <[email protected]> wrote:
>
> - ...
> - Object::getClass returns a predictable ref-mirror (I always wanted
> that)
>
> (aside: Yes, although in the case of `Foo.val value = ...;
value.getClass()`, I'll still claim it shouldn't compile or should at least
throw, so the user will write whichever of `Foo.class` or `Foo.val.class`
they actually want.
The surprising outcome of this is we now have (by my count) five buckets.
>
Sounds alarming, but mostly we just have to ensure that the individual
levers ("value", "non-atomic", visibility) are fully understandable
individually and orthogonally, with their combinations acting as expected
from that understanding. So long as we achieve that, the tallied up number
(5 or 7 or...) doesn't matter as much.
--
Kevin Bourrillion | Java Librarian | Google, Inc. | [email protected]
