Bitten by the lambda parameter name

Remi Forax forax at
Mon Jul 15 08:28:20 PDT 2013

On 07/15/2013 05:13 PM, Maurizio Cimadamore wrote:
> On 15/07/13 15:52, Remi Forax wrote:
>> This snippet not compile,
>>     Kind kind = ...
>>     partySetMap.computeIfAbsent(kind, kind -> new 
>> HashSet<>()).add(party);
>> Each time I write more than a hundred lines of codes that use some 
>> lambdas,
>> I fall into this trap.
>> It's very annoying !
>> Rémi
> Annoying yes - but there is a reason for it? If we provide special 
> scoping for lambda parameters then we will never be able to add 
> control abstraction syntax in a nice way; not saying that it's 
> something we want - but it's good to have option open at least.

It's a crystal ball argument, in the future if we do that then ...
It usually doesn't work because between now and the future, the way the 
feature will be introduced will change.

In this peculiar case, if we add control abstraction syntax we will use 
a different syntax,
so it's very annoying for no reason.

> Maurizio


More information about the lambda-dev mailing list