IntIterator

[Brian Goetz]

In general, we'd like to minimize the set of classes we make public, 
ideally the *Stream classes and the minimum necessary that they pull in. 
  The "SPI" (the Op classes and supporting types) are definitely going 
to be private for 8, though we would like to get them to the point where 
we can open it up for anyone to build ops.  This may mean collapsing the 
various subpackages of j.u.stream.

Exposing IntIterator would be unfortunate because it invites users to 
"pull on the string" and ask "where's IntIterable", "where's IntList", 
"where's IntArrayList", etc.

We'd like for what we release to be as "closed" as possible in the 
topological sense.

On 12/14/2012 11:30 AM, Paul Sandoz wrote:
>
> On Dec 14, 2012, at 5:15 PM, Remi Forax <forax at univ-mlv.fr> wrote:
>
>> The current prototype declare a class IntIterator in java.util.stream.primitive,
>> What is the status of this package ?
>>
>
> Ongoing... it changed today, I consolidated IntIterator into PrimitiveIterator.
>
>
>> I don't think you need to make it visible for users, it can be used internally without being exported and seen by everyone.
>> You can also remove the method iterator() and spliterator() from IntIterator given those are escape hatch and that users
>> can already do boxed().iterator() and boxed().spliterator().
>>
>
> Library writers/integrators may need to create primitive streams from appropriate sources and it would be nice to avoid boxing on the input.
>
> In source repo tip PrimitiveStreams is the primitive version of Streams.
>
> Paul.
>