Re: [boost] Is there interest in an "iofiber" library?

Subject: Re: [boost] Is there interest in an "iofiber" library?
From: David Sankel (camior_at_[hidden])
Date: 2019-01-05 22:53:51

On Sat, Jan 5, 2019 at 2:57 AM Vinícius dos Santos Oliveira <
vini.ipsmaker_at_[hidden]> wrote:

> Em sex, 4 de jan de 2019 Ã s 21:16, David Sankel <camior_at_[hidden]>
> escreveu:
>
>> This may be a dumb question, but could ASIO's stackful coroutine
>> completion token be extended to have
>>
>
> I could change ASIO's stackful coroutine completion token to have the
> functionality I need (maybe with some small breakage), but I don't want to
> increase the burden maintenance on Chris' back. That's basically the
> motivation to avoid sending a PR and starting a new lib.
>
> Maybe other problems would be:
>
>
>    - The dependency on C++11 (e.g. fiber objects are move-only handles
>    just like thread objects). ASIO is a C++98 library.
>    - Scope-creep within ASIO?
>
>
It seems like it would be a good idea to broach the subject with Chris to
see what his thoughts are. It seems like this is a replacement for
something that already exists in ASIO. He may be happy to see this live in
another library.

>
> the functionality you need?
>>
>
> I'm not the only one who needs this functionality. I'm not the only one
> avoiding Boost.Fiber because integration with ASIO is problematic. I'm not
> the only one reinventing thread patterns and cancellation patterns on top
> of ASIO's completion token. Others are doing it independently.
>

I didn't say the functionality *only* you need. ;-)