Enum Mode 

#[non_exhaustive]
pub enum Mode {
    StandardReadRemoteWrites(Box<StandardReadRemoteWrites>),
    DataBoostReadLocalWrites(Box<DataBoostReadLocalWrites>),
}

Which type of read needs to consistently observe which type of write? Default: standard_read_remote_writes

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

StandardReadRemoteWrites(Box<StandardReadRemoteWrites>)

Checks that reads using an app profile with StandardIsolation can see all writes committed before the token was created, even if the read and write target different clusters.

DataBoostReadLocalWrites(Box<DataBoostReadLocalWrites>)

Checks that reads using an app profile with DataBoostIsolationReadOnly can see all writes committed before the token was created, but only if the read and write target the same cluster.

Trait Implementations

impl Clone for Mode

fn clone(&self) -> Mode

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for Mode

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

Formats the value using the given formatter.

impl PartialEq for Mode

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

Tests for self and other values to be equal, and is used by ==.

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

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for Mode