Struct optimistic_lock_coupling::OptimisticLockCoupling

pub struct OptimisticLockCoupling<T: ?Sized> { /* fields omitted */ }

Our data structure, the usage is ‘pretty much’ same as RwLock

Implementations

impl<T> OptimisticLockCoupling<T>

pub fn new(t: T) -> Self

create an instance of OLC

pub fn read_txn<F, R>(&self, logic: F) -> OptimisticLockCouplingResult<R> where
    F: FnMut(&OptimisticLockCouplingReadGuard<'_, T>) -> OptimisticLockCouplingResult<R>, 

read transaction logic should be an inlined closure

impl<T: ?Sized> OptimisticLockCoupling<T>

pub fn make_outdate(&self)

make self outdate usually used when the container grows and this pointer point to this structure is replaced

pub fn is_poisoned(&self) -> bool

is writter thread dead? if fail then fail ~ no need extra sync

pub fn read(
    &self
) -> OptimisticLockCouplingResult<OptimisticLockCouplingReadGuard<'_, T>>

I suggest you redo the hole function when error occurs Or just use read_txn

pub fn write(
    &self
) -> OptimisticLockCouplingResult<OptimisticLockCouplingWriteGuard<'_, T>>

get your RAII write guard

Trait Implementations

impl<T: ?Sized + Default> Default for OptimisticLockCoupling<T>

fn default() -> Self

Returns the “default value” for a type.

impl<T: Sized> From<T> for OptimisticLockCoupling<T>

fn from(t: T) -> Self

Performs the conversion.

impl<T: ?Sized + Send> Send for OptimisticLockCoupling<T>

Of course Lock could be Send

impl<T: ?Sized + Send + Sync> Sync for OptimisticLockCoupling<T>

Of course Lock could be Sync