CoroGB
libunifex
CoroGB | libunifex | |
---|---|---|
3 | 22 | |
48 | 1,370 | |
- | 2.8% | |
0.0 | 7.6 | |
over 2 years ago | 11 days ago | |
C++ | C++ | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
CoroGB
-
Gameboy emulator written in C++
Nice - I also did a C++ Gameboy emulator with winapi - but I used coroutines, so it looks completely different: https://github.com/TheThief/CoroGB
-
C++20 coroutines seem baffling
The low level stuff can be used to wait on non-traditional things. For example, to learn C++ coroutines I made a gameboy emulator that uses coroutines for the different hardware components which can "await" a number of emulated clock cycles - and then a central scheduler handles advancing the clock and resuming coroutines as their awaited cycle comes up.
-
Do people have some motivating examples for co-routines?
A Gameboy emulator that uses coroutines and custom awaitable types to handle component scheduling: https://github.com/TheThief/CoroGB
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
What are some alternatives?
coproto - A protocol framework based on coroutines
cppcoro - A library of C++ coroutine abstractions for the coroutines TS
concurrencpp - Modern concurrency for C++. Tasks, executors, timers and C++20 coroutines to rule them all
noufu - GameBoy emulator with debugger written in C++ using Win32 and SDL2
Taskflow - A General-purpose Parallel and Heterogeneous Task Programming System
Web - Old experimental web server using fibers, io completion ports, and some early C++11 features.
Restbed - Corvusoft's Restbed framework brings asynchronous RESTful functionality to C++14 applications.
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.
corrade - C++11 multiplatform utility library
Boost.Beast - HTTP and WebSocket built on Boost.Asio in C++11
Folly - An open-source C++ library developed and used at Facebook.