rcoro
concurrencpp
| rcoro | concurrencpp | |
|---|---|---|
| 2 | 16 | |
| 21 | 2,058 | |
| - | - | |
| 5.5 | 1.2 | |
| about 2 months ago | 6 days ago | |
| C++ | C++ | |
| zlib License | 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.
rcoro
-
Sane coroutine imitation with macros; copyable, serializable, and with reflection
For future work ideas, I'd love to see this optimize well at -O1 and not only -O2.
concurrencpp
-
Is anyone using coroutines seriously?
I am using concurrencpp for my project. What I like about it is that it's basically a thread pool factory with coroutines. It allows for better structuring / organizing of multithreaded work. So for me the main advantage of coroutines is that the code looks easier to follow
- Concurrencpp – a C++20 library for coroutines and executors
-
Comparing asio to unifex
Equivalent concurrencpp code:
-
Do you think the current asynchronous models (executors, senders) are too complicated and really we just need channels and coroutines running on a thread pool?
I agree. I use concurrencpp for the exact use case you described - coroutines running on simple-to-understand-executors which return some asynchronous pipe for communication.
- concurrencpp version 0.1.6 has been released!
-
What happens if you co_await a std::future, and why is it a bad idea? - The Old New Thing
If you look at concurrencpp, you can control exactly where and how coroutines are resumed, using executors.
-
Collecting the best C++ practices
concurrencpp. Modern concurrency for C++. Tasks, executors, timers and C++20 coroutines to rule them all.
-
C++ Coroutines from scratch - Phil Nash - Meeting C++ 2022
Just use a good third party library like concurrencpp .
-
Header-only C++14 quality thread pool
Hi, I am looking for a header-only C++14 (or lower) quality thread pool. Ideally, it would be similar to BS::thread_pool but in C++14. Most of them I find on GitHub are bloated (e.g. concurrencpp) or have many open Issues. Ideal usage would be similar to:
-
Good repos for beginners to browse that follow best modern C++ practices (including testing, static analysis etc...)
I use concurrencpp for my asynchronous code and the repo is written in modern cpp, with tests, sanitizers and what not.
What are some alternatives?
qcoro - C++ Coroutines for Qt
libunifex - Unified Executors
cppcoro - A library of C++ coroutine abstractions for the coroutines TS
asio-grpc - Asynchronous gRPC with Asio/unified executors
Rstein.AsyncCpp - The RStein.AsyncCpp library is a set of types that should be familiar for anyone who knows the Task Parallel Library (TPL) for .NET (C#).
sobjectizer - An implementation of Actor, Publish-Subscribe, and CSP models in one rather small C++ framework. With performance, quality, and stability proved by years in the production.
coop - C++20 coroutines-based cooperative multitasking library
PhotonLibOS - Probably the fastest coroutine lib in the world!
fiber - C++20 fiber implementation with similar interface to std::thread, header-only / x86_64 / Linux only / stackful / built-in scheduler / thread shareable
coost - A tiny boost library in C++11.
ue5coro - A gameplay-focused C++17/20 coroutine implementation for Unreal Engine 5.
Forkpool - A bleeding-edge, lock-free, wait-free, continuation-stealing tasking library. [Moved to: https://github.com/ConorWilliams/libfork]