Skip to main content

Module rules

Module rules 

Source
Available on crate feature proptest only.
Expand description

The model rules. See the module documentation for what the family does, and each rule for what it rejects.

Each rule takes impl AsyncFn() -> F, as the worked-example rules do, and calls it once per node of every scenario: each call must be a fresh, isolated peer.

Functions§

forwarding_order_is_arrival_order
SY-25: a peer hands back what it holds in the order it arrived. The first occurrence of each event in a peer’s log follows the order the model saw it first offered.
redelivery_of_an_accepted_group_is_a_no_op
SY-11: re-delivering an event a peer already holds is a no-op. Every push is acknowledged with exactly as many appended events as the peer had never been offered, and exactly as many skipped as it had; and no peer holds any event twice.
transitive_convergence_over_a_partial_mesh
SY-24 and SY-4: after every link heals and the peers settle, every peer holds every event written anywhere, byte for byte — including peers that never met the event’s origin.