Remi Forax forax at
Sun Mar 24 14:44:42 PDT 2013

On 03/24/2013 08:32 PM, Sam Pullara wrote:
> I was working with Brian on seeing how limit/substream
> functionality[1] might be implemented and he suggested conversion to
> Iterator was the right way to go about it. I had thought about that
> solution but didn't find any obvious way to take an iterator and turn
> it into a stream. It turns out it is in there, you just need to first
> convert the iterator to a spliterator and then convert the spliterator
> to a stream. So this brings me to revisit the whether we should have
> these hanging off one of Iterable/Iterator directly or both.
> My suggestion is to at least have it on Iterator so you can move
> cleanly between the two worlds and it would also be easily
> discoverable rather than having to do:
> Spliterator.ORDERED))
> Sam
> [1]

It's not really a good sign of the heath of the API.

it seems that for a lot of problems there is no way to write a good 
Spliterator directly,
i.e. it's better to write an Iterator and let the JDK create the 
Spliterator around it,


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