Crates.io | lock_cell |
lib.rs | lock_cell |
version | 0.6.0 |
source | src |
created_at | 2023-06-24 21:57:23.719775 |
updated_at | 2023-07-08 07:19:12.172338 |
description | A custom locking cell type written in Rust |
homepage | |
repository | https://github.com/burtonageo/lock_cell |
max_upload_size | |
id | 899138 |
size | 30,684 |
This crate provides the LockCell<T>
and other supportings types.
A LockCell
is a cell type which provides dynamic mutation using interior
mutability. It is similar to RefCell<T>
, except that it only allows
a single borrow type (a lock). Locking a LockCell
allows mutating its
contents freely.
A LockCell
can only be used in a single threaded context - it cannot be shared
across different threads. Generally, a LockCell
will be stored in a Rc<T>
so that it can be shared.
Whether you use a LockCell
or a RefCell
depends on the structure and behavior of
your program. Generally, if you have a lot of writers and readers, using a LockCell
may be better, as it ensures that writers are less likely to be starved.
The Sync
equivalent of a LockCell
is Mutex<T>
.
The enable_std
feature enables the standard library. This provides an implementation of
std::error::Error
for the TryLockError
type. This feature is enabled by default.
The debug_lockcell
feature tracks the location of each lock()
call in the LockCell
,
allowing the developer to compare the first lock location in their file to the panicking
lock location, aiding in debugging.