On Wed, Jun 17, 2015 at 1:36 AM, Paul Sandoz 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-spliter
On Jun 17, 2015, at 8:10 AM, Martin Buchholz wrote:
>
> On Tue, Jun 16, 2015 at 1:43 AM, Paul Sandoz wrote:
>
> It's a subtle area. Certain Spliterator characteristics refer to the
> (element) source namely, NONULL, IMMUTABLE and CONCURRENT.
>
> Yes, it's subtle. I went back and studied
>
On Tue, Jun 16, 2015 at 1:43 AM, Paul Sandoz wrote:
>
> It's a subtle area. Certain Spliterator characteristics refer to the
> (element) source namely, NONULL, IMMUTABLE and CONCURRENT.
>
Yes, it's subtle. I went back and studied
http://download.java.net/jdk9/docs/api/java/util/Spliterator.ht
On Jun 15, 2015, at 7:31 PM, Martin Buchholz wrote:
> On Mon, Jun 15, 2015 at 10:16 AM, Paul Sandoz wrote:
> On Jun 15, 2015, at 6:34 PM, Martin Buchholz wrote:
> > Staring at LinkedTransferQueue.java, I see:
> >
> > return Spliterators.spliterator
> >
On Mon, Jun 15, 2015 at 10:16 AM, Paul Sandoz
wrote:
> On Jun 15, 2015, at 6:34 PM, Martin Buchholz wrote:
> > Staring at LinkedTransferQueue.java, I see:
> >
> > return Spliterators.spliterator
> > (a, 0, i, (Spliterator.ORDERED |
> >
On Jun 15, 2015, at 6:34 PM, Martin Buchholz wrote:
> Staring at LinkedTransferQueue.java, I see:
>
> return Spliterators.spliterator
> (a, 0, i, (Spliterator.ORDERED |
>Spliterator.NONNULL |
>
