Hi Paul, Thanks for the response and the link -- will look at it later.
I presume it in part might relate to cracking open the lambda “box” > implementing the targeted functional interface to obtain the underlying > method containing the lambda body, generated by javac, that the box defers > to, then subsituting the indy call to an invocation of that underlying > method. Cue lots of hand waving… Yes, that's sort of what I assumed it referred to. That would be great! Thanks On Tue, Nov 3, 2015 at 7:32 AM, Paul Sandoz <[email protected]> wrote: > Hi Vitaly, > > Probably worth sending an email to the [email protected] > <mailto:[email protected]> > > > On 3 Nov 2015, at 13:09, Vitaly Davidovich <[email protected]> wrote: > > > > Yes, I had seen Chris' presentation as well. Certainly modularization > will > > help AOT in many ways. But, I'm particularly interested on the JIT side. > > What was meant by aggressive lambda inlining, for example? Can anyone > point > > at some additional info? > > > > I presume it in part might relate to cracking open the lambda “box” > implementing the targeted functional interface to obtain the underlying > method containing the lambda body, generated by javac, that the box defers > to, then subsituting the indy call to an invocation of that underlying > method. Cue lots of hand waving… > > Maybe more clues in Oleg Pliss’s Closures on Embedded JVM presentation at > JVMLS 2014: > > http://www.oracle.com/technetwork/java/jvmls2014pliss-2265210.pdf < > http://www.oracle.com/technetwork/java/jvmls2014pliss-2265210.pdf> > > Paul. > >
