#map #owned #reference #guard

mapped-guard

Returnable guards that represent for example a subset of the original borrow. Implemented for the standard guard types and easily extensible.

1 unstable release

0.0.1 Sep 29, 2020

#9 in #guard

Download history 782/week @ 2020-12-29 492/week @ 2021-01-05 223/week @ 2021-01-12 111/week @ 2021-01-19 958/week @ 2021-01-26 36/week @ 2021-02-02 583/week @ 2021-02-09 55/week @ 2021-02-16 38/week @ 2021-02-23 53/week @ 2021-03-02 21/week @ 2021-03-09 19/week @ 2021-03-16 197/week @ 2021-03-23 570/week @ 2021-03-30 447/week @ 2021-04-06 22/week @ 2021-04-13

1,417 downloads per month
Used in 2 crates (via rhizome)

MIT/Apache

10KB
102 lines

mapped-guard

Lib.rs Crates.io Docs.rs

Rust 1.40.0 Build Status Crates.io - License

GitHub open issues open pull requests crev reviews

Returnable guards that represent for example a subset of the original borrow. Implemented for the standard guard types and easily extensible.

Installation

Please use cargo-edit to always add the latest version of this library:

cargo add mapped-guard

Example

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
);

A note on the implementation

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.

License

Licensed under either of

at your option.

Contribution

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.

Code of Conduct

Changelog

Versioning

mapped-guard strictly follows Semantic Versioning 2.0.0 with the following exceptions:

  • The minor version will not reset to 0 on major version changes (except for v1).
    Consider it the global feature level.
  • The patch version will not reset to 0 on major or minor version changes (except for v0.1 and v1).
    Consider it the global patch level.

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.

No runtime deps