Spliterator documentation

[Paul Sandoz]

Hi,

Various places in java.util and java.util.concurrent need to clarify the stuff about spliterators.

The lambda webrev linked to below tweaks stuff in java.util, assuming folks are OK with this i can also propose something for java.util.concurrent to be considered for 166:

  http://cr.openjdk.java.net/~psandoz/lambda/split-docs/webrev/

- the spliterators for empty Set/SortedSet/List/Map (+ NavigableMap/NavigableSet in tl) and singleton Set//List/Map don't conform to the reporting of characteristics for the correspond collection, they all reuse the empty or singleton spliterator implementation. I think it reasonable to relax the constraints on reporting certain characteristics here since with zero or 1 element there is not much clients can do regarding processing based on characteristics.

- i still have not come up with an alternative name for "fail-fast", contrary to some opinions on the related email thread about this i do think we need to mention it. I updated spliterator to mention about bulk traversal and checking for co-modification after all elements have been traversed.

Paul.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/lambda-libs-spec-experts/attachments/20130731/52150c4d/attachment.html