Module chalk_solve::rust_ir

source ·
Expand description

Contains the definition for the “Rust IR” – this is basically a “lowered” version of the AST, roughly corresponding to [the HIR] in the Rust compiler.

Structs§

  • AdtDatum
  • AdtDatumBound
  • AdtFlags
  • AdtRepr
  • AdtSizeAlign
    Information about the size and alignment of an ADT.
  • AdtVariantDatum
  • AliasEqBound
    Represents an alias equality bound on e.g. a type or type parameter. Does not know anything about what it’s binding.
  • AssociatedTyDatum
    Represents an associated type declaration found inside of a trait:
  • AssociatedTyDatumBound
    Encodes the parts of AssociatedTyDatum where the parameters P0..Pm are in scope (bounds and where_clauses).
  • AssociatedTyValue
    Represents the value of an associated type that is assigned from within some impl.
  • AssociatedTyValueBound
  • AssociatedTyValueId
    Identifier for an “associated type value” found in some impl.
  • CoroutineDatum
    Represents a coroutine type.
  • CoroutineInputOutputDatum
    The nested types for a coroutine. This always appears inside a CoroutineDatum
  • CoroutineWitnessDatum
    The coroutine witness data. Each CoroutineId has both a CoroutineDatum and a CoroutineWitnessDatum - these represent two distinct types in Rust. CoroutineWitnessDatum is logically ‘inside’ a coroutine - this only matters when we treat the witness type as a ’constituent type for the purposes of determining auto trait implementations.
  • CoroutineWitnessExistential
    The coroutine witness types, together with existentially bound lifetimes. Each ‘witness type’ represents a type stored inside the coroutine across a yield. When a coroutine type is constructed, the precise region relationships found in the coroutine body are erased. As a result, we are left with existential lifetimes - each type is parameterized over some lifetimes, but we do not know their precise values.
  • DefaultImplDatum
  • DefaultImplDatumBound
  • FnDefDatum
    A rust intermediate representation (rust_ir) of a function definition/declaration. For example, in the following rust code:
  • FnDefDatumBound
    Represents the bounds on a FnDefDatum, including the function definition’s type signature and where clauses.
  • FnDefInputsAndOutputDatum
    Represents the inputs and outputs on a FnDefDatum. This is split from the where clauses, since these can contain bound lifetimes.
  • ImplDatum
  • ImplDatumBound
  • OpaqueTyDatum
    Represents the bounds for an impl Trait type.
  • OpaqueTyDatumBound
  • TraitBound
    Represents a trait bound on e.g. a type or type parameter. Does not know anything about what it’s binding.
  • TraitDatum
    A rust intermediate representation (rust_ir) of a Trait Definition. For example, given the following rust code:
  • TraitDatumBound
  • TraitFlags

Enums§

  • AdtKind
  • ClosureKind
    Indicates the “most permissive” Fn-like trait that the closure implements. If the closure kind for a closure is FnMut, for example, then the closure implements FnMut and FnOnce.
  • ImplType
  • InlineBound
    An inline bound, e.g. : Foo<K> in impl<K, T: Foo<K>> SomeType<T>.
  • Movability
  • Polarity
  • WellKnownTrait
    A list of the traits that are “well known” to chalk, which means that the chalk-solve crate has special, hard-coded impls for them.

Traits§

Type Aliases§