On Jan 3, 2018, at 6:40 PM, John Rose wrote:
>
> (In L-world, a U-type appears to the JVM as an L-type, often an actual
> L-descriptor like "Lpkg.Foo;". The term U-type refers to a new way of
> using of L-type values. Likewise, R-types also appear to the JVM as
> L-types, but the term R-type re
(here's some of the "more later")
On Dec 13, 2017, at 11:58 AM, Karen Kinnear wrote:
>
> …
> V. Expected Behaviors:
>
> …
>
> 2. Java level APIs
> isValue
There are a few places where we can ask whether something is a value:
1. Given a U-type(*) variable x, is that variable's current value
On Jan 3, 2018, at 8:59 AM, Karen Kinnear wrote:
>
> Many thanks.
>
> A couple of points:
>>
>> Example: A field of value type either needs an explicit flatten flag,
>> or a Q-descriptor. The flatten flag (ACC_VALUE) makes an unambiguous
>> context for the L-descriptor of the field type, so t
The following was received on valhalla-spec-comments (archived at
http://mail.openjdk.java.net/pipermail/valhalla-spec-comments/2017-December/02.html).
Yes, such an operation is necessary both for generic code ("return the
default value for the type corresponding to type variable T"), and
Many thanks.
A couple of points:
>
> Example: A field of value type either needs an explicit flatten flag,
> or a Q-descriptor. The flatten flag (ACC_VALUE) makes an unambiguous
> context for the L-descriptor of the field type, so that it means a Q-type
> rather than an L-type.
Just to clarify:
Happy New Year!
Attendees: Remi, Dan H, Tobi, Dan S, John, Karen
AIs:
All - review nestmates JVMS invokeinterface selection changes
All - review Dan’s proposal for constant pool structural descriptors
Remi - proposal for T-Types - simpler approach to generic specialization
I. Nestmates
1. JVMTI