Enum NameProblem 

#[non_exhaustive]
pub enum NameProblem {
    Empty,
    Slash,
    Nul,
    Dots,
    Taken,
}

Why a name cannot be used, as the person types it.

More reasons may be added, so match with a _ arm and lean on message for the words.

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

Nothing, or only spaces, was typed.

Slash

It holds a /, which would make it a path rather than a name.

Nul

It holds a character no file name can hold.

Dots

It is . or .., which already mean this folder and the one above it.

Taken

An entry of the folder already has it.

Implementations

impl NameProblem

pub fn message(&self) -> String

What is wrong, in the person’s language.

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 Debug 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