Non interference enforcement

Remi Forax forax at
Wed Sep 26 06:26:35 PDT 2012

We currently ask users to write lambdas that doesn't interfere with the 
source collection
of a stream but it's not enforced in the code.

By example, -> { list.remove(e); });
may works or not depending how the pipeline is implemented.

This is a serous departure for the current way java.util collections works
and I wonder if we should not keep the fail-fast guarantee for those 


More information about the lambda-libs-spec-observers mailing list