libunifex
cppcoro
libunifex | cppcoro | |
---|---|---|
22 | 24 | |
1,366 | 3,241 | |
2.5% | - | |
7.6 | 0.0 | |
10 days ago | 4 months ago | |
C++ | C++ | |
GNU General Public License v3.0 or later | 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.
libunifex
-
Comparing asio to unifex
I'm curious what led you to this conclusion. If you ran into scalability issues with its static_thread_pool, then that's a known issue. If it's something else, the authors (of which I'm one) would love to know.
-
How does one actually build a C++ project
Instead of calling add_executable you will call add_library. Here is a (only moderately complicated) production example of a library that can be built standalone (along with tests and example executables), or as a subproject, where it builds only the library
-
How to write networking code now that will be easiest to adapt to the upcoming standard?
My original thought was to build my DDS implementation on top of libunifex in anticipation for standardization: https://github.com/facebookexperimental/libunifex
-
Executors/libunifex example project
I'm trying to understand how to work with the proposed executors in a project, but after watching Eric Niebler's cppcon talks (https://youtu.be/xLboNIf7BTg) and looking at the libunifex examples (https://github.com/facebookexperimental/libunifex/tree/main/examples) I still have a hard time wrapping my head around how to employ the sender/receiver pattern in a larger project.
-
Async/Await pattern in C++
You have coroutines in C++20 but there is also the executives proposal that's making it's way into C++23 that is available as a library under the name unifex that only requires C++14
-
Using Asio for asynchronous gRPC clients and servers
Asio-grpc makes exactly that possible by providing an Asio execution_context compatible interface to the CompletionQueue. It supports all types of RPCs (including generic ones), completion tokens, cancellation, as well as libunifex sender/receiver (if you want to try out what might become std::execution). The latest release (v1.7.0) also introduced a GrpcStream class for writing Rust/Golang select-style code.
-
My thoughts and dreams about a standard user-space I/O scheduler
P2300: they are trying to standardize facebookexperimental/libunifex
-
"C++ makes it harder to shoot yourself, but when you do it blows your whole leg off"
All the network handling for Instagram and all other Meta apps on all platforms is handled by their own C++ library https://github.com/facebookexperimental/libunifex.
-
State of the art for CPOs (customization points) in C++?
This. I'd also like to mention libunifex. It's entirely based on tag_invoke and is a testament as to how much power it actually provides. On the other hand, it also proves how cumbersome it is to define CPOs with tag_invoke. But IMO it's a lot better than anything else anyone has ever created, and users usually don't need to define new CPOs, only library writers do, so there's that.
-
Why do we need networking, executors, linear algebra, etc in the Standard Library?
A work in progress implementation of the library: https://github.com/facebookexperimental/libunifex
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?
concurrencpp - Modern concurrency for C++. Tasks, executors, timers and C++20 coroutines to rule them all
drogon - Drogon: A C++14/17/20 based HTTP web application framework running on Linux/macOS/Unix/Windows
Taskflow - A General-purpose Parallel and Heterogeneous Task Programming System
Folly - An open-source C++ library developed and used at Facebook.
Restbed - Corvusoft's Restbed framework brings asynchronous RESTful functionality to C++14 applications.
C-Coroutines - Coroutines for C.
corrade - C++11 multiplatform utility library
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.
Boost.Beast - HTTP and WebSocket built on Boost.Asio in C++11
coproto - A protocol framework based on coroutines
uvloop - Ultra fast asyncio event loop.