mir::[−][src] interpret:: error
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
rustc_mir::interpret, we have
macros for this.
Details of an access to uninitialized bytes where it is not allowed.
Details of why a pointer had to be in-bounds.
Error information for when the program we executed turned out not to actually be a valid program. This cannot happen in stand-alone Miri, but it can happen during CTFE/ConstProp where we work on generic code or execution does not have all information available.
Error information for when the program exhausted the resources granted to it by the interpreter.
Error information for when the program caused Undefined Behavior.
Error information for when the program did something that might (or might not) be correct to do according to the Rust spec, but due to limitations in the interpreter, the operation could not be carried out. These limitations can differ between CTFE and the Miri engine, e.g., CTFE does not support dereferencing pointers at integral addresses.
A trait to work around not having trait object upcasting.
A trait for machine-specific errors (or other “machine stop” conditions).