>All this is to say, what you are saying sounds like a difficultly
>with one
>or more implementations, and not with the logic of the spec. Am I
>missing
>something?
I haven't seen a rationale for the proposed spec change yet (maybe I
missed it?) which only leaves implementation costs as a discuss
On Feb 27, 2018, at 10:12 AM, Tobi Ajila wrote:
>
> > 4. arrays
> > We need a new bytecode to create a flattenable/non-nullable array
> > existing bytecodes do not create flattenable arrays with the new model of
> > container marking flattenable
> > rather than by type
> On a related note, it mi
> 4. arrays
> We need a new bytecode to create a flattenable/non-nullable array
> existing bytecodes do not create flattenable arrays with the new model of
container marking flattenable
> rather than by type
On a related note, it might be worth it to also consider the implication of
flattened arra
On Feb 20, 2018, at 7:52 AM, Karen Kinnear wrote:
>
> attendees: Tobi, Mr Simms, Dan H, Dan S, Frederic, Remi, Karen
>
> ...
> III. Value Types
>
> Latest LWorld Value Types proposal:
> http://cr.openjdk.java.net/~acorn/LWorldValueTypesFeb13.pdf
> Latest rough draft JVMS:
> http://cr.openjdk.
> On Feb 20, 2018, at 7:52 AM, Karen Kinnear wrote:
>
> attendees: Tobi, Mr Simms, Dan H, Dan S, Frederic, Remi, Karen
>
> I. Condy
>
> 1. Condy reference implementation was pushed last week into JDK 11.
>
A next round of development will focus on the BootstrapCallInfo API and BSM
invocati
er (static) though we'd like to avoid the former
> (instance).
thanks,
Karen
>
> --Dan
>
> - Original message -
> From: Karen Kinnear
> Sent by: "valhalla-spec-experts"
>
> To: valhalla-spec-experts
> Cc:
> Subject: Re: Valhalla EG minutes
On Feb 21, 2018, at 10:51 AM, Daniel Heidinga
wrote:
>
> By "private methods" does that imply both static and instance methods? I
> hope not.
>
> With NestMates, the JVMS has been updated with the (non-normative) text:
> ---
> Because private methods may now be invoked from a nestmate clas
Thanks Karen for the link to the bug.
By "private methods" does that imply both static and instance methods? I hope not.
With NestMates, the JVMS has been updated with the (non-normative) text:
---
Because private methods may now be invoked from a nestmate class, it is no longer recommended
JVMTI RedefineClasses spec handling of private methods is being tracked via:
https://bugs.openjdk.java.net/browse/JDK-8192936
thanks,
Karen
> On Feb 20, 2018, at 10:52 AM, Karen Kinnear wrote:
>
> attendees: Tobi, Mr Simms, Dan H, Dan S, Frederic, Remi, Karen
>
> I. Condy
>
> 1. Condy refere
> 3. Planned uses for condy in jdk?
> - Nothing in imminent plans
> - expect longer term constant Lambdas to use condy - lightweight
> - future: still exploring APIs for constants, switch, pattern match, …
Using condy for method references and stateless lambdas could happen relatively
soon
attendees: Tobi, Mr Simms, Dan H, Dan S, Frederic, Remi, Karen
I. Condy
1. Condy reference implementation was pushed last week into JDK 11.
2. StackOverFlow handling/future LDC early cycle detection
Dan S walked us through his StackOverFlow JVMS clarification for condy,
specifically the orderin
11 matches
Mail list logo
