Updated State of the Lambda
Brian Goetz
brian.goetz at oracle.com
Fri Oct 15 13:52:06 PDT 2010
We do go a few bridges in another direction, as you saw -- but in my opinion
the _ placeholder is indeed a bridge too far for Java. (Works fine in Scala
-- and its OK to not turn Java into Scala. Different languages, different
philosophies, so its OK if they draw the line in different places.)
Cheers,
-Brian
On 10/15/2010 4:46 PM, Luc Duponcheel wrote:
> All,
>
> great stuff
>
> the end of the article shows support for simple expressions like
>
> |Collections.sortBy(people, #{ p -> p.getLastName() }); |
>
> what about going one step further and use the (both loved and hated)
> underscore syntax of Scala
>
> |Collections.sortBy(people, #{ _.getLastName() });|
>
> Or would that be one bridge to far?
>
> Luc
>
>
> On Fri, Oct 15, 2010 at 9:55 PM, Brian Goetz <brian.goetz at oracle.com
> <mailto:brian.goetz at oracle.com>> wrote:
>
> An updated draft (Version 3) of the State of the Lambda has been published at:
>
> http://cr.openjdk.java.net/~briangoetz/lambda/lambda-state-3.html
> <http://cr.openjdk.java.net/%7Ebriangoetz/lambda/lambda-state-3.html>
>
> Notable differences from the previous draft include:
> - 'this' in lambda expressions is lexically scoped
> - 'yield' keyword dropped in favor of 'return'
> - new syntax
>
> Maurizio will be pushing an implementation conforming to this draft soon.
>
>
>
>
>
> --
> __~O
> -\ <,
> (*)/ (*)
>
> reality goes far beyond imagination
>
More information about the lambda-dev
mailing list