Module rules
Available on non-WebAssembly only.
Expand description
The rules of the concurrency family.
Each has the same shape as an event-store rule — async fn(open) -> RuleOutcome — and differs only in the bound on F::Store. None of them is
capability-gated: a fixture that cannot hand out CONTENDERS handles onto
one store already fails CF-16’s MUST in the event-store family.
Every one of them reads back what its contenders wrote, so each settles the
frontier after the contenders have joined and before its observer reads
(CF-42). That is the one way any of them returns
RuleOutcome::Skipped: under
READ_YOUR_OWN_WRITES, for a fixture that declines it and cannot settle.
Functions§
- a_
busy_ append_ left_ nothing_ behind - An append answered
Busyleft nothing in the store. - a_
concurrent_ reader_ never_ sees_ a_ partial_ batch - A reader running against a live writer never sees part of a batch.
- append_
returns_ the_ callers_ own_ last_ position appendreturns the caller’s own last position, not the store’s head.- exactly_
one_ of_ n_ contenders_ commits - Of
CONTENDERShandlers that decided from one snapshot, exactly one commits. - k_
disjoint_ boundaries_ never_ conflict - Contenders on different consistency boundaries do not conflict.
- positions_
are_ unique_ under_ concurrent_ appends - Concurrent unconditional appends never share a position.