pub trait CompareAndSetOrdering {
// Required methods
fn success(&self) -> Ordering;
fn failure(&self) -> Ordering;
}👎Deprecated:
compare_and_set and compare_and_set_weak that use this trait are deprecated, use compare_exchange or compare_exchange_weak insteadExpand description
Memory orderings for compare-and-set operations.
A compare-and-set operation can have different memory orderings depending on whether it succeeds or fails. This trait generalizes different ways of specifying memory orderings.
The two ways of specifying orderings for compare-and-set are:
- Just one
Orderingfor the success case. In case of failure, the strongest appropriate ordering is chosen. - A pair of
Orderings. The first one is for the success case, while the second one is for the failure case.
Required Methods§
Sourcefn success(&self) -> Ordering
👎Deprecated: compare_and_set and compare_and_set_weak that use this trait are deprecated, use compare_exchange or compare_exchange_weak instead
fn success(&self) -> Ordering
compare_and_set and compare_and_set_weak that use this trait are deprecated, use compare_exchange or compare_exchange_weak insteadThe ordering of the operation when it succeeds.
Sourcefn failure(&self) -> Ordering
👎Deprecated: compare_and_set and compare_and_set_weak that use this trait are deprecated, use compare_exchange or compare_exchange_weak instead
fn failure(&self) -> Ordering
compare_and_set and compare_and_set_weak that use this trait are deprecated, use compare_exchange or compare_exchange_weak insteadThe ordering of the operation when it fails.
The failure ordering can’t be Release or AcqRel and must be equivalent or weaker than
the success ordering.