Bitten by the lambda parameter name

[Maurizio Cimadamore]

On 16/07/13 16:40, Peter Levart wrote:
> Could be efficiently stored in the Map like other entries (using 
> special private key), but the same problem exists like with 
> computeIfAbsent. Such default method could only work with 
> "cooperating" Map implementations and not with any Map... 
Perhaps the trick is to use some method you can call on the map to get a 
map-with-default out of it. Pretty much like Collections.synchronizedMap

Maurizio