On Wed, Jun 17, 2015 at 1:36 AM, Paul Sandoz <paul.san...@oracle.com> wrote:
> > > """A top-level Spliterator should not report both CONCURRENT and > IMMUTABLE, since they are mutually exclusive. Such a Spliterator is > inconsistent and no guarantees can be made about any computation using that > Spliterator. Sub-spliterators may report IMMUTABLE if additions or removals > to the source are not reflected when traversing.""" > > > Yes, sub-spliterators may additionally report. > > I guess i don't have a strong opinion on modifying sub-spliterators of > certain concurrent collections to additionally report IMMUTABLE. My > inclination is not to bother but i would not strongly object if someone > else did :-) > I agree with you that it probably doesn't matter much in practice. But we're trying to create very high quality software here, and there should be a clear way of deciding when to report IMMUTABLE, and at least in openjdk proper we should be consistent about it.
