pub enum PathStyle {
Expr,
Type,
Mod,
}
Expand description
Specifies how to parse a path.
Variants
Expr
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.
Type
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.
Mod
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
impl StructuralPartialEq for PathStyle
Auto Trait Implementations
impl RefUnwindSafe for PathStyle
impl Send for PathStyle
impl Sync for PathStyle
impl Unpin for PathStyle
impl UnwindSafe for PathStyle
Blanket Implementations
sourceimpl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
const: unstable · sourcefn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Layout
Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...)
attributes. Please see the Rust Reference’s “Type Layout” chapter for details on type layout guarantees.
Size: 1 byte
Size for each variant:
Expr
: 0 bytesType
: 0 bytesMod
: 0 bytes