Struct InterpErrorInfo 

pub struct InterpErrorInfo<'tcx>(Box<InterpErrorInfoInner<'tcx>>);

Packages the kind of error we got from the const code interpreter up with a Rust-level backtrace of where the error occurred. These should always be constructed by calling .into() on an InterpError. In rustc_mir::interpret, we have throw_err_* macros for this.

Interpreter errors must not be silently discarded (that will lead to a panic). Instead, explicitly call discard_err if this is really the right thing to do. Note that if this happens during const-eval or in Miri, it could lead to a UB error being lost!

Tuple Fields

0: Box<InterpErrorInfoInner<'tcx>>

Implementations

impl<'tcx> InterpErrorInfo<'tcx>

pub fn into_parts(self) -> (InterpErrorKind<'tcx>, InterpErrorBacktrace)

pub fn into_kind(self) -> InterpErrorKind<'tcx>

pub fn from_parts( kind: InterpErrorKind<'tcx>, backtrace: InterpErrorBacktrace, ) -> Self

pub fn kind(&self) -> &InterpErrorKind<'tcx>

pub fn to_string(&self) -> String

Turn the given error into a human-readable string. Expects the string to be printed, so if RUSTC_CTFE_BACKTRACE is set this will show a backtrace of the rustc internals that triggered the error.

This is NOT the preferred way to render an error; use report from const_eval instead. However, this is useful when error messages appear in ICEs.

Trait Implementations

impl<'tcx> Debug for InterpErrorInfo<'tcx>

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

Formats the value using the given formatter.

impl From<ErrorHandled> for InterpErrorInfo<'_>

fn from(err: ErrorHandled) -> Self

Converts to this type from the input type.

impl<'tcx> From<InterpErrorInfo<'tcx>> for ValTreeCreationError<'tcx>

fn from(err: InterpErrorInfo<'tcx>) -> Self

Converts to this type from the input type.

impl<'tcx> From<InterpErrorKind<'tcx>> for InterpErrorInfo<'tcx>

fn from(kind: InterpErrorKind<'tcx>) -> Self

Converts to this type from the input type.

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