2 unstable releases

0.1.0 Jun 2, 2022
0.0.1 Jun 2, 2022

#885 in Concurrency

Download history 84/week @ 2024-03-12 52/week @ 2024-03-19 114/week @ 2024-03-26 83/week @ 2024-04-02 2/week @ 2024-05-28

84 downloads per month

MIT license

154 lines


Crates.io Docs.rs Build Status CodeCov.io

Just a Sync alternative to std::cell::RefCell. Useful when you have a value to share between tasks/closures, and you already know or guarantee that the access to the value is safe (for example, via choir task dependencies).

The cost of borrowing is a single atomic operation, and it's riguriously checked by both Loom and Miri.


Rust already has tools for sharing values between threads, but it strikes me that they are all rather involved and complicated:

Shareable mutable containers exist to permit mutability in a controlled manner, even in the presence of aliasing. Both Cell<T> and RefCell<T> allow doing this in a single-threaded way. However, neither Cell<T> nor RefCell<T> are thread safe (they do not implement Sync). If you need to do aliasing and mutation between multiple threads it is possible to use Mutex<T>, RwLock<T> or atomic types.

This paragraph from std::cell documentation proposes to use lock-based primitives as an alternative in Sync world. But what if you just need sharing without locking, and still want safety? SynCell comes to help.


~329K SLoC