Is there interest in an "iofiber" library?

2 Jan 2019

      I have written a completion token for Boost.Asio that is a little more
advanced than plain ASIO's spawn featuring abstractions such as join(),
detach() and even interrupt().

I'd like to know if there is interest in seeing this library merged as part
of Boost.

https://vinipsmaker.github.io/iofiber/

(there is also a mutex and a semaphore, but these are undocumented as of
now and were poorly ported from the previous token supporting abstractions
and need rework)

Boost.Fiber integration with ASIO is problematic:
https://github.com/boostorg/fiber/issues/102#issuecomment-263558882

Default Boost.Asio yield token will do as long as you don't need
communication between fibers. When primitive communication is necessary,
you can work around it by exploiting the completion token protocol. In
fact, after having rolled my own solution, I eventually was made aware of
Peter's solution (which he rolled on his own independently) which was
incredibly similar to my solution:
https://github.com/equalitie/ouinet/blob/a2afaf9932c8a23434d1f0a10be06fc4077...

If you need anything more advanced such as careful strand integration,
join, or interruption API, you'll just have to roll your own token. That's
what I end up doing after working around ASIO's token for many months.

There was also a recent request by Vinnie to turn Boost.Coroutine 1
deprecation warning off. This separate library would be an alternative
(although it is still a far from review-ready).

-- 
Vinícius dos Santos Oliveira
https://vinipsmaker.github.io/

Vinícius dos Santos Oliveira

David Sankel

Vinícius dos Santos Oliveira

David Sankel

Oliver Kowalke

tags

participants (3)