Enum rustc_middle::mir::interpret::error::InterpError

pub enum InterpError<'tcx> {
    UndefinedBehavior(UndefinedBehaviorInfo<'tcx>),
    Unsupported(UnsupportedOpInfo),
    InvalidProgram(InvalidProgramInfo<'tcx>),
    ResourceExhaustion(ResourceExhaustionInfo),
    MachineStop(Box<dyn MachineStopType>),
}

Variants

UndefinedBehavior(UndefinedBehaviorInfo<'tcx>)

Tuple Fields

0: UndefinedBehaviorInfo<'tcx>

The program caused undefined behavior.

Unsupported(UnsupportedOpInfo)

Tuple Fields

0: UnsupportedOpInfo

The program did something the interpreter does not support (some of these might be UB but the interpreter is not sure).

InvalidProgram(InvalidProgramInfo<'tcx>)

Tuple Fields

0: InvalidProgramInfo<'tcx>

The program was invalid (ill-typed, bad MIR, not sufficiently monomorphized, …).

ResourceExhaustion(ResourceExhaustionInfo)

Tuple Fields

0: ResourceExhaustionInfo

The program exhausted the interpreter’s resources (stack/heap too big, execution takes too long, …).

MachineStop(Box<dyn MachineStopType>)

Tuple Fields

0: Box<dyn MachineStopType>

Stop execution for a machine-controlled reason. This is never raised by the core engine itself.

Implementations

impl InterpError<'_>

pub fn formatted_string(&self) -> bool

Some errors do string formatting even if the error is never printed. To avoid performance issues, there are places where we want to be sure to never raise these formatting errors, so this method lets us detect them and bug! on unexpected errors.

pub fn is_hard_err(&self) -> bool

Should this error be reported as a hard error, preventing compilation, or a soft error, causing a deny-by-default lint?

Trait Implementations

impl Debug for InterpError<'_>

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

Formats the value using the given formatter.

impl Display for InterpError<'_>

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

Formats the value using the given formatter.

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

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

Performs the conversion.

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

Size for each variant:

• UndefinedBehavior: 63 bytes
• Unsupported: 39 bytes
• InvalidProgram: 87 bytes
• ResourceExhaustion: 1 byte
• MachineStop: 23 bytes