Crates.io | with_lock |
lib.rs | with_lock |
version | 0.5.4 |
source | src |
created_at | 2021-10-31 14:45:25.20235 |
updated_at | 2022-05-26 19:27:58.631133 |
description | Deadlock freedom |
homepage | |
repository | https://github.com/Milo123459/with_lock |
max_upload_size | |
id | 474749 |
size | 13,297 |
Deadlock freedom
Using with_lock? Share it in the discussion!
This crate provides a simple way of managing Mutex's, and freeing your code from deadlocks. It is powered by parking_lot.
Say you have this code:
use std::sync::Mutex;
fn main() {
let a = Mutex::new(2);
let b = Mutex::new(3);
let a_lock = a.lock().unwrap();
let b_lock = b.lock().unwrap();
assert_eq!(*a_lock + *b_lock, 5);
let a_lock_2 = a.lock().unwrap();
let b_lock_2 = b.lock().unwrap();
assert_eq!(*a_lock_2 + *b_lock_2, 5);
}
That code will run the first assert_eq!
fine, but the second wouldn't assert due to a deadlock.
However, we can prevent this by replacing our manual calls of .lock
with .with_lock
. Code that wouldn't error would look something like:
use with_lock::WithLock;
fn main() {
let a = WithLock::<i64>::new(2);
let b = WithLock::<i64>::new(3);
let a_lock = a.with_lock(|s| *s);
let b_lock = b.with_lock(|s| *s);
assert_eq!(a_lock + b_lock, 5);
let a_lock_2 = a.with_lock(|s| *s);
let b_lock_2 = b.with_lock(|s| *s);
assert_eq!(a_lock_2 + b_lock_2, 5);
}
This test would pass, and both assertions would be fulfilled. This is an example of how a dead lock was prevented.
with_lock
provides a custom Cell
like API powered by a Mutex.
use with_lock::MutexCell;
fn main() {
let a = MutexCell::new(2);
let b = MutexCell::new(3);
let a_locked = a.get();
let b_locked = b.get();
assert_eq!(a_locked + b_locked, 5);
let a_lock_2 = a.get();
let b_lock_2 = b.get();
assert_eq!(a_lock_2 + b_lock_2, 5);
}
For more examples, see the examples directory.
They can be run by cloning this repository and running cargo run --example <example_name>
.