Enum ScenarioMismatch 

#[non_exhaustive]
pub enum ScenarioMismatch {
    Counts {
        expected: ElementCounts,
        got: ElementCounts,
    },
    BusOrder,
}

Why a gridfm scenario snapshot doesn’t line up with the first snapshot’s base element set (the row-stack keeps every table schema-consistent by requiring the same element counts and bus-id ordering across snapshots).

#[non_exhaustive]: future checks (e.g. branch endpoints, voltage base) may add variants, so downstream matches must keep a wildcard arm.

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.

Counts

Element counts differ.

Fields

expected: ElementCounts

got: ElementCounts

BusOrder

Counts match, but the buses are listed in a different order (so the dense bus index wouldn’t mean the same bus across snapshots).

Trait Implementations

impl Clone for ScenarioMismatch

fn clone(&self) -> ScenarioMismatch

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for ScenarioMismatch

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

Formats the value using the given formatter.

impl Display for ScenarioMismatch

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

Formats the value using the given formatter.

impl PartialEq for ScenarioMismatch

fn eq(&self, other: &ScenarioMismatch) -> 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 Copy for ScenarioMismatch

impl Eq for ScenarioMismatch

impl StructuralPartialEq for ScenarioMismatch