Enum PathProblem 

#[non_exhaustive]
pub enum PathProblem {
    NamesNothing,
    Magic,
    Absolute,
    Relative,
    TrailingSlash,
    Glob(char),
    BadComponent,
}

Why a path token is not a literal, root-relative file or directory. git ls-tree does not glob, so a wildcard would match nothing and silently fingerprint nothing; every other shape here is a path git would interpret rather than look up.

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.

NamesNothing

? alone.

Magic

Starts with :, git’s pathspec magic.

Absolute

Starts with /.

Relative

Starts with ./ or ../.

TrailingSlash

Ends with /.

Glob(char)

Contains a glob or escape character.

BadComponent

Has an empty, . or .. component.

Trait Implementations

impl Clone for PathProblem

fn clone(&self) -> Self

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for PathProblem

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

Formats the value using the given formatter.

impl Display for PathProblem

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

Formats the value using the given formatter.

impl Eq for PathProblem

impl PartialEq for PathProblem

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

Equality operator ==.

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

Inequality operator !=.

impl StructuralPartialEq for PathProblem