[squeak-dev] Re: Generators on Streams on Generators on
Collections on ...
Robert Withers
robert.w.withers at gmail.com
Tue Apr 12 20:07:33 UTC 2016
In my case I think of this as draining what has collected. How about #drainAvailable?
---
robert
> On Apr 12, 2016, at 15:44, Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com> wrote:
>
> Hi Marcel,
> So what are you trying to achieve?
> Is it something like (self nextAvailable: infinitelyMany)?
> -- fetch as much as possible from the stream, but don't block (wait) --
>
> 2016-04-12 19:43 GMT+02:00 marcel.taeumel <Marcel.Taeumel at hpi.de>:
>> Hi Bert,
>>
>> yes. I made that so.
>>
>> It remains a question about
>>
>> #collectInfinitely:
>> #selectInfinitely:
>> #gatherInfinitely:
>> #rejectInfinitely:
>> #upToNil
>>
>> If you wrap this stuff around SocketStream, you can re-used even after a
>> time window without data.
>>
>> So, should we remove it or keep it? It already is in trunk, if you don't
>> know what I refer to.
>>
>> Best,
>> Marcel
>>
>>
>>
>> --
>> View this message in context: http://forum.world.st/Generators-on-Streams-on-Generators-on-Collections-on-tp4889389p4889611.html
>> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20160412/e3e65459/attachment.htm
More information about the Squeak-dev
mailing list
|