Skip to main content

Module rules

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 Busy left 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
append returns the caller’s own last position, not the store’s head.
exactly_one_of_n_contenders_commits
Of CONTENDERS handlers 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.