Dividing Streams.java

Tim Peierls tim at peierls.net
Thu Apr 11 16:13:44 PDT 2013


Agreed. What harm is there in parceling the Spliterator stuff off?

On Thu, Apr 11, 2013 at 7:01 PM, Joe Bowbeer <joe.bowbeer at gmail.com> wrote:

> But I am (and represent) Joe Programmer, and I've already complained :O
>
> At the top of the list is the confusing name doubleParallelStream, which
> does not create two parallel streams!
>
> It's very difficult to find anything useful in there, and the ones that
> take Spliterator arguments are a devil to figure out how to use, which adds
> to Joe's frustration.
>
> Simply removing everything that references a spliterator thing cleans it
> up a lot.
>
>
> On Thu, Apr 11, 2013 at 3:49 PM, Doug Lea <dl at cs.oswego.edu> wrote:
>
>> On 04/11/13 13:51, Brian Goetz wrote:
>>
>>> Joe quite correctly pointed out in the survey that Streams.java is a mix
>>> of two
>>> things for two audiences:
>>>
>>>   - Utility methods for users to generate streams, like intRange()
>>>   - Low level methods for library writers to generate streams from
>>> things like
>>> iterators or spliterators.
>>>
>>>
>> I'm not too tempted by this. Classes Collections and Arrays have lots
>> of stuff and people don't seem to complain.
>>
>> -Doug
>>
>>
>


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