cppcoro
cppcoro copied to clipboard
Does anyone still maintain this library under their own branch?
The library seems to have been abandoned
So far the only one I found is this one: https://github.com/andreasbuhr/cppcoro
But that seems to also be no longer maintained
Yes, I am sorry. Would be great if someone picked it up.
So far the only one I found is this one: https://github.com/andreasbuhr/cppcoro
But that seems to also be no longer maintained
It's a pity that this library has been abandoned
Yes, I am sorry. Would be great if someone picked it up.
Is there an alternative to this lib somewhere at the moment?
Indeed a pitty. Today I found this https://github.com/David-Haim/concurrencpp Maybe that's you (and me) might build on...
You may also have a look at https://github.com/facebookexperimental/libunifex
Thanks! Do you have experience with this library? Can I use it as a coroutine library without changing my paradigm to sender/receiver (at least for a first shot)?
Thanks! Do you have experience with this library? Can I use it as a coroutine library without changing my paradigm to sender/receiver (at least for a first shot)?
I just discovered it... No experience
I'm also working on this https://github.com/ladnir/macoro A subset of this library along with c++14 support.
FYI: A better coroutine lib and IO framework https://github.com/alibaba/PhotonLibOS
https://github.com/alibaba/async_simple @nqf @duckdoom5 @andreasbuhr
Not quite a 100% replacement, but a project with a very similar objective is asyncpp. It also comes with extensions for interfacing with curl, grpc and io_uring.
The core library is header only and tested on Windows, Linux and MacOS to ensure it supports as many compilers/environments as possible. It is used in a number of internal projects, so I will almost certainly support it for a long time going forward. It is allocator ready and comes with some extra helpers (like a reference counting type, pointer tagging, etc).
Its not as feature complete as cppcoro or some of the earlier mentioned libraries, but it is complete enough (at least for me) and I am open to any improvements/addition someone wants to add.
Disclamer: I wrote it, so my view might be biased.
Pinging people that might care: @nqf @duckdoom5 @andreasbuhr @devillove084