Skip to main content

condition_rejection_leaves_store_unchanged

Function condition_rejection_leaves_store_unchanged 

pub async fn condition_rejection_leaves_store_unchanged<F: Fixture>(
    open: impl AsyncFn() -> F,
) -> RuleOutcome
Expand description

A rejected append changes nothing observable.

Strengthened where a second handle exists: “nothing observable” is a claim about the store, not about the connection that made the attempt, and an adapter that rolls back its own session while leaving a shared cache dirty passes the single-handle version. As above this is a strengthening, so the rule reports Ran either way.

§The before guard, and why it belongs to this rule

Stage 3 left this open: the rule compares two reads for equality, and two empty reads are equal, so a store whose reads return nothing passed it — InnerJoinTagStore did. The argument for leaving it was that the rule’s subject is the rejection rather than the read.

The guard lands here anyway, because the subject is not “the append was rejected”, it is “the store is unchanged”, and an unchanged store is only observable if there was something there to be unchanged. Equality over nothing is the same vacuity read_defaults_to_ascending_order’s length check exists to remove — windows(2) over an empty slice is vacuously ordered — and it is one line in both places.