cs_libguarded
concurrent-resource
Our great sponsors
| cs_libguarded | concurrent-resource | |
|---|---|---|
| 10 | 2 | |
| 218 | 19 | |
| 0.0% | - | |
| 5.0 | 2.0 | |
| about 1 month ago | 10 months ago | |
| C++ | C++ | |
| 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.
cs_libguarded
- MutexProtected: A C++ Pattern for Easier Concurrency
-
Using shared_ptr for reloadable config
I know this article was trying to come up with an excuse to use a shared_ptr, but atomic smart pointers are a lot more error prone than wrapping mutexes in an appropriate interface that hides the complexity and forces you to use them correctly.
-
Ban thread locking classes/functions?
The approach I would recommend would be to use mutexes but wrap them in a convenience library designed to make them difficult to misuse: https://github.com/copperspice/cs_libguarded
-
FreeRTOS Guarded Data Structure
I was inspired by the great copperspice library libguarded and wanted something similar for when I have to go back to micro's and FreeRTOS. The basic idea of the library is to prevent access to a shared data structure unless the mutex lock associated with it is also acquired. This is to prevent situations where someone forgets to get the lock before reading or writing to shared memory.
-
Strategies for serialization of a class in a concurrent fashion
I'm personally partial to the basic guarded type from https://github.com/copperspice/cs_libguarded due to its simplicity.
-
Why Rust mutexes look like they do
The Rust strategy for mutexes sounds a lot like libguarded, which now that I've read this article is occurs to me that the former was likely have been the inspiration for the latter.
This is pretty much what libguarded does.
-
How would you recommend implementing an iterator that holds a resource?
Also I don't think that operating this way is good to begin with. See how libGuard operates - it is way way cleaner and more flexible https://github.com/copperspice/cs_libguarded
-
A C++ locking wrapper
have you heard of https://github.com/copperspice/cs_libguarded ? it sounds like a similar idea, but supports other stuff like rcu as well
-
Having fun overloading the operator->
https://github.com/copperspice/cs_libguarded#cslibguarded
concurrent-resource
- concurrent-resource - non-intrusive thread safety for non-thread safe types
-
How would you recommend implementing an iterator that holds a resource?
Take a look into following library. It might give you an idea. https://github.com/mustafakemalgilor/concurrent-resource
What are some alternatives?
ultimatepp - U++ is a C++ cross-platform rapid application development framework focused on programmer's productivity. It includes a set of libraries (GUI, SQL, Network etc.), and integrated development environment (TheIDE).
air-ctl - C Language Template Library C语言 模板库
concurrencpp - Modern concurrency for C++. Tasks, executors, timers and C++20 coroutines to rule them all
Boost.Compute - A C++ GPU Computing Library for OpenCL
Folly - An open-source C++ library developed and used at Facebook.
Windows Terminal - The new Windows Terminal and the original Windows console host, all in the same place!
parking_lot - Compact and efficient synchronization primitives for Rust. Also provides an API for creating custom synchronization primitives.
scope - Boost.Scope, a collection of scope guard utilities.
lock_ios - iostream synchronization manipulator for concurrency
ThreadSafeVar - Simple wrapper to create thread safe variable with a mutex.
freertos-addons - Additions to FreeRTOS
rwspinlock - Slim, simple, cross-process, reader-writer unfair fast spin lock for Windows