Enum NameProblem 

#[non_exhaustive]
pub enum NameProblem {
    Empty,
    TooLong,
    LeadingChar,
    Character,
    ReservedDevice,
}

Why a string is not a usable database name.

A typed reason rather than a message, so a caller (and a test) can react to the specific problem instead of matching on prose.

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.

Empty

The name was empty.

TooLong

The name was longer than MAX_DB_NAME.

LeadingChar

The first character was neither a lowercase ASCII letter nor a digit. Leading -, _ and . are refused so a name can never be read as a flag or as a relative path component.

Character

Some character was outside [a-z0-9_-].

ReservedDevice

The name is a Windows device name (con, nul, com1, …). Refused everywhere so a workspace stays portable between machines.

Trait Implementations

impl Clone for NameProblem

fn clone(&self) -> NameProblem

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Copy for NameProblem

impl Debug for NameProblem

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

Formats the value using the given formatter.

impl Display for NameProblem

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

Formats the value using the given formatter.

impl Eq for NameProblem

impl PartialEq for NameProblem

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

Equality operator ==.

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

Inequality operator !=.

impl StructuralPartialEq for NameProblem