Enum rustc_middle::mir::interpret::error::InterpError [−][src]
pub enum InterpError<'tcx> {
UndefinedBehavior(UndefinedBehaviorInfo<'tcx>),
Unsupported(UnsupportedOpInfo),
InvalidProgram(InvalidProgramInfo<'tcx>),
ResourceExhaustion(ResourceExhaustionInfo),
MachineStop(Box<dyn MachineStopType>),
}
Variants
UndefinedBehavior(UndefinedBehaviorInfo<'tcx>)
The program caused undefined behavior.
Tuple Fields of UndefinedBehavior
0: UndefinedBehaviorInfo<'tcx>
Unsupported(UnsupportedOpInfo)
The program did something the interpreter does not support (some of these might be UB but the interpreter is not sure).
Tuple Fields of Unsupported
InvalidProgram(InvalidProgramInfo<'tcx>)
The program was invalid (ill-typed, bad MIR, not sufficiently monomorphized, …).
Tuple Fields of InvalidProgram
0: InvalidProgramInfo<'tcx>
ResourceExhaustion(ResourceExhaustionInfo)
The program exhausted the interpreter’s resources (stack/heap too big, execution takes too long, …).
Tuple Fields of ResourceExhaustion
MachineStop(Box<dyn MachineStopType>)
Stop execution for a machine-controlled reason. This is never raised by the core engine itself.
Tuple Fields of MachineStop
0: Box<dyn MachineStopType>
Implementations
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.
Should this error be reported as a hard error, preventing compilation, or a soft error, causing a deny-by-default lint?
Trait Implementations
Performs the conversion.
Auto Trait Implementations
impl<'tcx> !RefUnwindSafe for InterpError<'tcx>
impl<'tcx> !Send for InterpError<'tcx>
impl<'tcx> !Sync for InterpError<'tcx>
impl<'tcx> Unpin for InterpError<'tcx>
impl<'tcx> !UnwindSafe for InterpError<'tcx>
Blanket Implementations
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: 64 bytes
Size for each variant:
UndefinedBehavior
: 63 bytesUnsupported
: 39 bytesInvalidProgram
: 31 bytesResourceExhaustion
: 1 byteMachineStop
: 23 bytes