asyncly
cppcoro
asyncly | cppcoro | |
---|---|---|
2 | 24 | |
27 | 3,250 | |
- | - | |
5.0 | 0.0 | |
23 days ago | 4 months ago | |
C++ | C++ | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
asyncly
-
Why choose async/await over threads?
One of the main benefits of async/await in Rust is that it can work in situations where you don't even have threads or dynamic memory. You can absolutely use it to write very concise code that's waiting on an interrupt on your microcontroller to have read some data coming in over I2C from some buffer. It's a higher level abstraction that allows your code to use concurrency (mostly) without having tons of interactions with the underlying runtime.
Every major piece of software that I have worked on has implemented this in one form or another (even in non-modern C++ where you don't have any coroutine concepts, Apple's grand central dispatch,). If you don't then your business logic will either be very imperformantly block on IO, have a gazillion of threads that make development/debugging a living hell, or be littered with implementation details of the underlying runtime or a combination of all 3.
If you don't use existing abstractions in the language (or through some library), you will end up building them yourselves, which is hard and probably overall inferior to widely used ones (if there are any). I have done so in the past, see https://github.com/goto-opensource/asyncly.
-
David Mazieres' tutorial and take on C++20 coroutines
Keep in mind that these is a really basic building block where you can bring your own runtime and hook coroutines into it, not something that is at all usable out of the box. This is exacerbated by the fact that the C++ standard library is still lacking support for non-blocking futures/promises.
To see how it can be used for actual asynchronous operations on a thread pool, take a look at asyncly, which I co-authored:
https://github.com/LogMeIn/asyncly/blob/master/Test/Unit/fut...
cppcoro
-
Struggle with C++ 20 Coroutines
PS: Take a look at cppcoro; this might help as well, especially generator<>, if you're looking to generate numbers, and stuff;
-
Does C++23 have a coroutine task promise type?
This is the only viable implementation.
-
Stop Comparing Rust to Old C++
Kind of sounds like whatever library you were using provided leaky abstractions. Something like cppcoro provides really good abstractions for coroutines, the user really doesn't need to understand why any of it works.
-
Sane coroutine imitation with macros; copyable, serializable, and with reflection
Is there a usecase for copying/serializing such coroutines? If not, I would use the normal C++20 coroutines (cppcoro?).
-
Is Tokio::sync::Mutex lock-free?
C++ has the popular CppCoro library. Async_mutex is its equivalent of Tokio::sync::Mutex, providing exclusive access to data shared between tasks.
- My experience with C++ 20 coroutines
-
My thoughts and dreams about a standard user-space I/O scheduler
Because the whole application is running under a single thread there is no need for atomic operations in synchronization primitives(which most of the time requires seq_cst memory order and CMPXCHG which is an expensive instruction in CPU). for example what async_mutex would look like if it knows it's running in a single-threaded scheduler (a non-atomic state variable and waiters queue).
-
[Discussion] What are some old C++ open source projects you wish were still active?
Maybe not old, but I wish cppcoro was still updated. It was such a nice start!
-
A high-level coroutine explanation
You can get generator<> from https://github.com/lewissbaker/cppcoro
-
C++ Coroutines Do Not Spark Joy
It is possible to compose them more easily than described in the article; Lewis Baker's cppcoro library for example provides a recursive_generator<> type[0] that allows this without using any macros. It's up to the library part of coroutines to make things easy, end users are not expected to write low-level coroutine code themselves.
I wonder about the allocation elision. Return value optimization became mandatory, and some compilers can already elide calls to new/delete and malloc()/free() in normal code, so perhaps it will be possible to guarantee allocation elision in the future in the most used cases.
[0]: https://github.com/lewissbaker/cppcoro#recursive_generatort
What are some alternatives?
C-Coroutines - Coroutines for C.
libunifex - Unified Executors
coro-chat - Playing with the C++17 Coroutines TS to implement a simple chat server
drogon - Drogon: A C++14/17/20 based HTTP web application framework running on Linux/macOS/Unix/Windows
Folly - An open-source C++ library developed and used at Facebook.
Flow - Flow is a software framework focused on ease of use while maximizing performance in closed closed loop systems (e.g. robots). Flow is built on top of C++ 20 coroutines and utilizes modern C++ techniques.
coproto - A protocol framework based on coroutines
uvloop - Ultra fast asyncio event loop.
cppcoro - A library of C++ coroutine abstractions for the coroutines TS
coro - Coroutine library and toolkit for C++20