pub struct Expr {
pub id: NodeId,
pub kind: ExprKind,
pub span: Span,
pub attrs: AttrVec,
pub tokens: Option<LazyAttrTokenStream>,
}
Expand description
An expression.
Fields§
§id: NodeId
§kind: ExprKind
§span: Span
§attrs: AttrVec
§tokens: Option<LazyAttrTokenStream>
Implementations§
source§impl Expr
impl Expr
sourcepub fn is_potential_trivial_const_arg(&self) -> bool
pub fn is_potential_trivial_const_arg(&self) -> bool
Is this expr either N
, or { N }
.
If this is not the case, name resolution does not resolve N
when using
min_const_generics
as more complex expressions are not supported.
Does not ensure that the path resolves to a const param, the caller should check this.
pub fn to_bound(&self) -> Option<GenericBound>
pub fn peel_parens(&self) -> &Expr
pub fn peel_parens_and_refs(&self) -> &Expr
pub fn precedence(&self) -> ExprPrecedence
pub fn take(&mut self) -> Self
sourcepub fn is_approximately_pattern(&self) -> bool
pub fn is_approximately_pattern(&self) -> bool
To a first-order approximation, is this a pattern?
Trait Implementations§
source§impl HasAttrs for Expr
impl HasAttrs for Expr
source§const SUPPORTS_CUSTOM_INNER_ATTRS: bool = false
const SUPPORTS_CUSTOM_INNER_ATTRS: bool = false
This is
true
if this HasAttrs
might support ‘custom’ (proc-macro) inner
attributes. Attributes like #![cfg]
and #![cfg_attr]
are not
considered ‘custom’ attributes. Read morefn attrs(&self) -> &[Attribute]
fn visit_attrs(&mut self, f: impl FnOnce(&mut AttrVec))
source§impl HasTokens for Expr
impl HasTokens for Expr
fn tokens(&self) -> Option<&LazyAttrTokenStream>
fn tokens_mut(&mut self) -> Option<&mut Option<LazyAttrTokenStream>>
Auto Trait Implementations§
impl !RefUnwindSafe for Expr
impl !Send for Expr
impl !Sync for Expr
impl Unpin for Expr
impl !UnwindSafe for Expr
Blanket Implementations§
source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere T: ?Sized,
source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more
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: 72 bytes