Struct rustc_infer::infer::canonical::ir::CoroutineClosureArgsParts

pub struct CoroutineClosureArgsParts<I>
where
    I: Interner,
{
    pub parent_args: <I as Interner>::GenericArgsSlice,
    pub closure_kind_ty: <I as Interner>::Ty,
    pub signature_parts_ty: <I as Interner>::Ty,
    pub tupled_upvars_ty: <I as Interner>::Ty,
    pub coroutine_captures_by_ref_ty: <I as Interner>::Ty,
    pub coroutine_witness_ty: <I as Interner>::Ty,
}

See docs for explanation of how each argument is used.

See CoroutineClosureSignature for how these arguments are put together to make a callable ty::FnSig suitable for typeck and borrowck.

Fields

parent_args: <I as Interner>::GenericArgsSlice

This is the args of the typeck root.

closure_kind_ty: <I as Interner>::Ty

Represents the maximum calling capability of the closure.

signature_parts_ty: <I as Interner>::Ty

Represents all of the relevant parts of the coroutine returned by this coroutine-closure. This signature parts type will have the general shape of fn(tupled_inputs, resume_ty) -> (return_ty, yield_ty), where resume_ty, return_ty, and yield_ty are the respective types for the coroutine returned by the coroutine-closure.

Use coroutine_closure_sig to break up this type rather than using it yourself.

tupled_upvars_ty: <I as Interner>::Ty

The upvars captured by the closure. Remains an inference variable until the upvar analysis, which happens late in HIR typeck.

coroutine_captures_by_ref_ty: <I as Interner>::Ty

a function pointer that has the shape for<'env> fn() -> (&'env T, ...). This allows us to represent the binder of the self-captures of the closure.

For example, if the coroutine returned by the closure borrows String from the closure’s upvars, this will be for<'env> fn() -> (&'env String,), while the tupled_upvars_ty, representing the by-move version of the same captures, will be (String,).

coroutine_witness_ty: <I as Interner>::Ty

Witness type returned by the generator produced by this coroutine-closure.

Layout

Note: Unable to compute type layout, possibly due to this type having generic parameters. Layout can only be computed for concrete, fully-instantiated types.