Mailing-List: contact dev-help@zest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zest.apache.org
Subject: Re: Stream creation...
To: dev@zest.apache.org
References: 
 <CADmm+Kdvo-J8md=f+-OfQWwJOH-RDOD38BMz0MPi6=a1JKBCiA@mail.gmail.com>
 <CADmm+KerXt4wPOZd9413kBcjtkKBVYZvQzK658GnrXVUvFzaSw@mail.gmail.com>
From: =?UTF-8?Q?Kent_S=c3=b8lvsten?= <kent.soelvsten@gmail.com>
Message-ID: <55E9964D.2000606@gmail.com>
Date: Fri, 4 Sep 2015 15:02:05 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: 
 <CADmm+KerXt4wPOZd9413kBcjtkKBVYZvQzK658GnrXVUvFzaSw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

It fixed a problem  in an Aggregate test (don't recall the exact name of
the test).

My guess is that the previous version was streaming and removing
concurrently
 - the new implementation finds all items that should be removed before
starting the actual removal.

/Kent


Den 04-09-2015 kl. 14:01 skrev Niclas Hedhman:
> I am also curious about this change;
>
> -        ).distinct().forEach( unitOfWork::remove );
> +        ).distinct().collect( Collectors.toList() ).stream().forEach(
> unitOfWork::remove );
>
> From my understanding it is the same thing (except slower). Do you recall
> what this is about?
>
>
> On Fri, Sep 4, 2015 at 7:56 PM, Niclas Hedhman <niclas@hedhman.org> wrote:
>
>> Kent,
>> while reviewing, I saw
>>
>>     Arrays.asList( type ).stream()
>>
>> This can more efficiently be written as
>>
>>     Stream.of( type )
>>
>> Cheers
>> --
>> Niclas Hedhman, Software Developer
>> http://zest.apache.org - New Energy for Java
>>
>
>