Lambdas and their overheads isn't much of an issue in the grand scheme
of things, but forcing the
initialization early when not much of the code java.lang.invoke depends
on has had a chance to at
least warm up somewhat does cause awkward hiccups in startup tests. Thus
it makes sense to defer
the first initialization somewhat, for now.
I hope we'll continue making these overheads smaller so that we in time
can use lambdas (or any
new language feature) anywhere without regressing even the most
synthetic startup tests.
/Claes
On 2017-12-13 21:17, Martin Buchholz wrote:
fyi Google does some automated desugaring for lambdas using a program
named ... desugar.
