Struct rustc_hir_typeck::closure::ExpectedSig

struct ExpectedSig<'tcx> {
    cause_span: Option<Span>,
    sig: PolyFnSig<'tcx>,
}

What signature do we expect the closure to have from context?

Fields

cause_span: Option<Span>

Span that gave us this expectation, if we know that.

sig: PolyFnSig<'tcx>

Trait Implementations

impl<'tcx> Clone for ExpectedSig<'tcx>

fn clone(&self) -> ExpectedSig<'tcx>

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl<'tcx> Debug for ExpectedSig<'tcx>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'tcx> TypeFoldable<TyCtxt<'tcx>> for ExpectedSig<'tcx>

fn try_fold_with<__F: FallibleTypeFolder<TyCtxt<'tcx>>>( self, __folder: &mut __F ) -> Result<Self, __F::Error>

The entry point for folding. To fold a value t with a folder f call: t.try_fold_with(f).

fn fold_with<F>(self, folder: &mut F) -> Selfwhere F: TypeFolder<I>,

A convenient alternative to try_fold_with for use with infallible folders. Do not override this method, to ensure coherence with try_fold_with.

impl<'tcx> TypeVisitable<TyCtxt<'tcx>> for ExpectedSig<'tcx>

fn visit_with<__V: TypeVisitor<TyCtxt<'tcx>>>( &self, __visitor: &mut __V ) -> ControlFlow<__V::BreakTy>

The entry point for visiting. To visit a value t with a visitor v call: t.visit_with(v).

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: 40 bytes