Enum Crash 

pub enum Crash {
    LosingUnsynced,
    KeepingEverything,
    Keeping(Vec<u64>),
}

Which unsynced writes survived a crash.

Variants

LosingUnsynced

None of them. The pessimistic case, and the one most tests reach for first.

KeepingEverything

All of them. Not a crash so much as a clean shutdown, and worth testing because a database that only works when writes are lost has a different bug.

Keeping(Vec<u64>)

Exactly these, by the sequence numbers from SimFilesystem::pending.

This is the variant the exhaustive enumeration uses. With three unsynced writes there are eight subsets and the test runs all eight.

Trait Implementations

impl Clone for Crash

fn clone(&self) -> Crash

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Crash

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Eq for Crash

impl PartialEq for Crash

fn eq(&self, other: &Crash) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for Crash