Re: JVMS draft for L-world value types with support for nullability

Hi Paul, > On Jan 31, 2018, at 15:50, Paul Sandoz wrote: > > Hi Fred, > > Some basic questions, which might be because the specification is > transitioning from value-based to value classes. > > >> The ACC_ENUM flag indicates that this class or its superclass is

Re: Final CONSTANT_Dynamic spec

> On Jan 18, 2018, at 5:14 PM, Dan Smith wrote: > > A proposed final spec for CONSTANT_Dynamic is here: > > http://cr.openjdk.java.net/~dlsmith/constant-dynamic.html > > There are two significant changes: > > 5.4.3: Expanded the rule about concurrent resolution to

Re: A "RecursiveConstants" attribute

It seems to me that the rational thing to do is, in SE 11, to implicitly assume max-depth is zero, and be done.  (IE, pretend to implement this proposal, but don't actually allow classfiles to have the attribute.)  Then we won't get any classfiles that have cycles, and the full spectrum of

JVMS draft for L-world value types with support for nullability

Here’s a draft of the JVMS proposing a way to implement the L-world value types, with support for value-based classes migration to value classes (essentially, support for nullability): http://cr.openjdk.java.net/~fparain/L-world/L-World-JVMS-3.pdf The assumptions and key properties are listed

Re: API Updates: 8191116: [Nestmates] Update core reflection, MethodHandle and varhandle APIs to allow for nestmate access

> On Jan 30, 2018, at 7:22 PM, David Holmes wrote: > > Hi Paul, > > On 31/01/2018 12:24 PM, Paul Sandoz wrote: >>> On Jan 30, 2018, at 1:55 AM, David Holmes >> > wrote: >>> >>> >>> MethodHandle API