Hiding the lambda proxy frame
Daniel_Heidinga at ca.ibm.com
Thu Jun 13 19:30:02 PDT 2013
> Introduce tail calls and use them in adapter code generated for
> lambdas. Then there's no confusion about the state of the JVM
> stack, since it is an operational change that all components would
> see in the same way. There would be the usual confusion with tail
> calls, about "how did I get here?"
I like this idea but its hard to argue that tail calls are in scope for
lambda. Tail calls should really be an entirely separate JSR. Addressing
these generated adaptor frames (and the other similar frames) is something
that should be left to that (future?) JSR.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lambda-spec-experts