Proposed API for JEP 259: Stack-Walking API
forax at univ-mlv.fr
Sat Oct 31 18:50:43 UTC 2015
Hi Mandy, hi all,
----- Mail original -----
> De: "Mandy Chung" <mandy.chung at oracle.com>
> À: "David M. Lloyd" <david.lloyd at redhat.com>
> Cc: core-libs-dev at openjdk.java.net
> Envoyé: Vendredi 30 Octobre 2015 21:39:38
> Objet: Re: Proposed API for JEP 259: Stack-Walking API
> > On Oct 30, 2015, at 12:59 PM, David M. Lloyd <david.lloyd at redhat.com>
> > wrote:
> > Clever/interesting way to prevent the stream from being used outside of the
> > stack frame it is active in. I was trying to think of a way it could be
> > subverted but I haven't come up with one yet.
> That’s John’s suggestion (John always has great ideas).
> > Since this is very likely to be a one-implementation API, is there a reason
> > to have a separate WalkerOption interface and Option enum? Seems like you
> > could just skip the interface.
> Locals and operands is one experimental feature in mind that is not target
> for JDK 9. But it would be an interesting feature for e.g. Fibers to
> experiment. This will also allow JDK-specific capability to be implemented
> in the future.
I think most of the runtime language developers, myself included will kill to have this feature included into the JDK.
There are several features of dynamic languages that are currently hard to implement like type specialization, stack reification, as you said fibers, and more generally de-optimization that will be far easier to implement with that capability (currently only Nashorn can afford to implement some of these optimizations).
More information about the core-libs-dev