And how does that differ from Point.class / Point.ref.class /
Point.class.noNotThatClassTheOtherClass() ?
I realize you're not necessarily asking that question in this thread,
but I want to walk through how I would respond to it anyway.
First here is what I already take to be tr
On Thu, Feb 10, 2022 at 4:25 AM Brian Goetz wrote:
I think this is a useful exercise anyway, though; we have stumbled over
> type-vs-class in a lot of places already with respect to B3, and int has
> similar problems; most uses of `int` are types, but there's also
> `int.class`, which means ... s
* Could the doc make a clearer distinction (throughout) between which
facts about int/Integer are happening because we expect *all* bucket-3
classes to work that way, vs. which are special one-off tweaks for the
8 predefined types?
A "how are int/Integer special" section would indeed be use
Some much-delayed feedback/questions
* Could the doc make a clearer distinction (throughout) between which facts
about int/Integer are happening because we expect *all* bucket-3 classes to
work that way, vs. which are special one-off tweaks for the 8 predefined
types?
* I'm curious whether it
I'm made some revisions to JEP 402 to better track with the revised JEP 401—in
particular backing off of "everything is an object".
There were some short-lived changes where I more aggressively pursued the idea
that the class was named 'int', but I've backed off of that, too. Now taking
the mor
