Module rustc_middle::mir::interpret::error
source · Macros§
Structs§
- Details of an access to uninitialized bytes / bad pointer bytes where it is not allowed.
- 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 anInterpError. Inrustc_mir::interpret, we havethrow_err_*macros for this. - Information about a misaligned pointer.
- Information about a size mismatch.
Enums§
- Details of which pointer is not aligned.
- 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 (except for layout errors that are only detect during monomorphization), 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.
Traits§
- A trait for machine-specific errors (or other “machine stop” conditions).
Functions§
Type Aliases§
Ok(Err(ty))indicates the constant was fine, but the valtree couldn’t be constructed because the value containts something of typetythat is not valtree-compatible. The caller can then show an appropriate error; the query does not have the necssary context to give good user-facing errors for this case.