Enum syntax::parse::parser::PathStyle[][src]

pub enum PathStyle {
    Expr,
    Type,
    Mod,
}

How to parse a path.

Variants

In some contexts, notably in expressions, paths with generic arguments are ambiguous with something else. For example, in expressions segment < .... can be interpreted as a comparison and segment ( .... can be interpreted as a function call. In all such contexts the non-path interpretation is preferred by default for practical reasons, but the path interpretation can be forced by the disambiguator ::, e.g. x<y> - comparisons, x::<y> - unambiguously a path.

In other contexts, notably in types, no ambiguity exists and paths can be written without the disambiguator, e.g. x<y> - unambiguously a path. Paths with disambiguators are still accepted, x::<Y> - unambiguously a path too.

A path with generic arguments disallowed, e.g. foo::bar::Baz, used in imports, visibilities or attributes. Technically, this variant is unnecessary and e.g. Expr can be used instead (paths in "mod" contexts have to be checked later for absence of generic arguments anyway, due to macros), but it is used to avoid weird suggestions about expected tokens when something goes wrong.

Trait Implementations

impl Copy for PathStyle
[src]

impl Clone for PathStyle
[src]

Returns a copy of the value. Read more

Performs copy-assignment from source. Read more

impl PartialEq for PathStyle
[src]

This method tests for self and other values to be equal, and is used by ==. Read more

This method tests for !=.

Auto Trait Implementations

impl Send for PathStyle

impl Sync for PathStyle