Re: Lightweight tasks to implement co-routines?

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 2017-08-01 06:56, Randy Brukardt wrote:
> "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> wrote in message
> news:olo5rp$dp0$1@gioia.aioe.org...
>> On 2017-07-31 20:08, Victor Porton wrote:
> ...
>> I have a vague idea that it should be an entry of some ad-hoc fake
>> protected object that would glue both calls together, or maybe an entry of
>> the "carrier" task. But I don't know how to make this easy to use and
>> encapsulated without exposing to other contexts.
> 
> Tucker Taft is proposing a construct called a "channel" for this purpose. It
> sounds interesting, but there are so few details it is impossible to tell.
> There is an AI for it (AI12-0197-4), but it is empty pending a real proposal
> from Tucker.

Yes, at least the use case is same.

One very important thing though. The construct cannot be statically 
nested as suggested. Consider the case when one producer distributes 
items among several consumers. As a practical example take a multiple 
socket select in the producer that then yields to one of the consumers 
to handle the active socket or else to process socket I/O data.

1. You don't know in advance how many consumers (connections) there will be.

2. There are multiple groups of identical consumers.

I am sure there could be cases with multiple producers as well.

This is why I thought that a task would be a much better way to express 
co-routine than some nested block.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de