Performance implications of the lambda draft specification

Joshua Bloch jjb at google.com
Fri Feb 19 17:09:14 PST 2010


John,

I've learned the hard way that this line of reasoning can lead to pain.
 When I designed the collections framework, I was assured that the cost of
creating and using an iterator to traverse an ArrayList would vanish due to
VM-wonderfulness.  That was 13 years ago.  I'm still waiting.

            Josh

On Fri, Feb 19, 2010 at 4:54 PM, John Nilsson <john at milsson.nu> wrote:

> On Fri, Feb 19, 2010 at 7:56 PM, Osvaldo Doederlein <opinali at gmail.com
> >wrote:
>
> > Having said that I'm enthusiastic about the upcoming EA-based scalar
> > replacement capability of JDK7, I've been testing it for a while. But
> much
> > less enthusiastic about designing a language feature that is very
> > important,
> > and would depend on that optimization.
>
>
> OTOH other JVM languages are already dependent on such optimizations. Doing
> the same for Java would only add one more to the family. If this leads to
> more resources being spent on such optimizations all JVM languages would
> benefit.
>
> BR,
> John
>
>


More information about the lambda-dev mailing list