Crates.io | mapped-guard |
lib.rs | mapped-guard |
version | 0.0.1 |
source | src |
created_at | 2020-09-29 13:15:30.981223 |
updated_at | 2020-09-29 13:15:30.981223 |
description | Returnable guards that represent for example a subset of the original borrow. Implemented for the standard guard types and easily extensible. |
homepage | https://github.com/Tamschi/mapped-guard/tree/v0.0.1 |
repository | https://github.com/Tamschi/mapped-guard |
max_upload_size | |
id | 294093 |
size | 29,209 |
Returnable guards that represent for example a subset of the original borrow. Implemented for the standard guard types and easily extensible.
Please use cargo-edit to always add the latest version of this library:
cargo add mapped-guard
use core::{fmt::Debug, ops::Deref};
use mapped_guard::MapGuard as _;
use std::sync::Mutex;
#[derive(Debug)]
struct Wrapper(usize);
let wrapper_mutex = Mutex::new(Wrapper(0));
/// # Panics
///
/// Iff `wrapper_mutex` is poisoned.
fn lock_increment(wrapper_mutex: &Mutex<Wrapper>) -> impl '_ + Deref<Target = usize> + Debug {
let mut guard = wrapper_mutex.lock().unwrap();
guard.0 += 1;
guard.map_guard(|wrapper| &wrapper.0)
};
assert_eq!(
*lock_increment(&wrapper_mutex),
1
);
This library is a workaround until mapped guards become available in the standard library and uses boxing internally.
While it's in practice likely possible to implement this more efficiently (without boxing) for many guards, this isn't safe except for mutable borrows where the documentation explicitly states they are write-through.
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
mapped-guard
strictly follows Semantic Versioning 2.0.0 with the following exceptions:
This includes the Rust version requirement specified above.
Earlier Rust versions may be compatible, but this can change with minor or patch releases.
Which versions are affected by features and patches can be determined from the respective headings in CHANGELOG.md.