marl
cgreenlet
| marl | cgreenlet | |
|---|---|---|
| 1 | 1 | |
| 1,781 | 81 | |
| 1.1% | - | |
| 5.7 | 10.0 | |
| 5 months ago | over 3 years 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.
marl
cgreenlet
-
Fiber in C++: Understanding the Basics
A disadvantage to the ‘no function coloring’ in fibers is that it makes lockless programming harder. A nested function call can switch from under you without your knowledge, making it hard to know where the preemption points are and whether to take locks when making updates to shared state. With function coloring you know exactly whether a function might switch or not.
I’ve programmed both fiber based systems and coroutines. I even created my own fiber libraries for Python (https://github.com/geertj/gruvi) and C++ (https://github.com/geertj/cgreenlet, mostly an experiment, and incorrectly named coroutines for C++ while it’s really fibers). In the Python version I experimented with some features to help you know whether a nested function might switch.
In the end, for me and for the problem domains I worked in, the explicit async/await co-routine style wins over fibers. It gives you most of the performance and memory benefits of user mode switching while keeping your code mostly lock free.
What are some alternatives?
stack-switching - A repository for the stack switching proposal.
context
gruvi - Async IO for Python, Simplified
ghost-userspace
assembly - assembly projects
llvm-project - The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
concurrencpp - Modern concurrency for C++. Tasks, executors, timers and C++20 coroutines to rule them all