clone_cell
clone_cell provides a Cell implementation that works with types whose Clone implementations are
guaranteed not to mutate the Cell content through the &self reference. This is enforced with the
provided PureClone trait, which is a subtrait of Clone (and a logical supertrait of Copy). It
is only implemented for types with compliant clone methods.
Overview
The Cell implementation provided by this crate is intended to be a drop-in replacement of
std::cell::Cell. It can work with types that behave like values, such as Rc<T>, Weak<T>
(shared pointers themselves are like values; it is the pointees that behave like references),
Option<T: PureClone>, and more. Some motivating use cases include implementing the observer
pattern and combining Cell with clone-on-write or immutable collections to enable efficient
sharing of data structures.
PureClone is currently implemented for the following types:
- All primitives such as
i32,usize,f64, etc; - References:
&T; Rc<T>andWeak<T>;Option<T: PureClone>; and- Tuples:
(A: PureClone, ...).
See PureClone for a complete list.
Examples
In this example below, we store an Rc<T> in a Cell and later retrieve a copy of it.
use Rc;
use Cell;
let x = new;
x.set;
assert_eq!;
See the documentation for Cell for more.
A proc macro is also provided to derive PureClone for user types safely.
use Rc;
use ;
// Note: This also generates a `Clone` impl.
let p = new;
let f = new;
f.set;
assert_eq!;
assert_eq!;
assert_eq!;
See the clone module documentation for more information.
Limitations
- Similar to
std::cell::Cell, thisCellis!Sync. - Since a new trait
PureCloneis used, there is no out-of-the-box support for types from third-party crates.
Soundness
I believe this is sound, because PureClone is unsafe to implement. This trait is implemented for:
Copytypes;- Types that perform a shallow clone such as
RcandWeak; and - Types whose
clonemethods are otherwise known to be safe, such as compound types that only containPureClonetypes.
See the documentation for more information. Please let me know if you find any soundness issues!
Contributing
Pull requests are welcome and any feedback is appreciated!