CoroGB
cppcoro
CoroGB | cppcoro | |
---|---|---|
3 | 24 | |
48 | 3,241 | |
- | - | |
0.0 | 0.0 | |
over 2 years 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.
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
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?
coproto - A protocol framework based on coroutines
libunifex - Unified Executors
noufu - GameBoy emulator with debugger written in C++ using Win32 and SDL2
drogon - Drogon: A C++14/17/20 based HTTP web application framework running on Linux/macOS/Unix/Windows
Web - Old experimental web server using fibers, io completion ports, and some early C++11 features.
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.
C-Coroutines - Coroutines for C.
uvloop - Ultra fast asyncio event loop.
coro-chat - Playing with the C++17 Coroutines TS to implement a simple chat server