Re-exports§
use std::any::Any;🔒use std::backtrace::Backtrace;🔒use std::borrow::Cow;🔒use std::convert;🔒use std::fmt;🔒use std::mem;🔒use std::ops;🔒use either::Either;🔒use rustc_abi::Align;🔒use rustc_abi::Size;🔒use rustc_abi::VariantIdx;🔒use rustc_data_structures::sync::Lock;🔒use rustc_errors::DiagArgValue;🔒use rustc_errors::ErrorGuaranteed;🔒use rustc_errors::IntoDiagArg;🔒use rustc_macros::StableHash;🔒use rustc_macros::TyDecodable;🔒use rustc_macros::TyEncodable;🔒use rustc_session::CtfeBacktrace;🔒use rustc_span::def_id::DefId;🔒use rustc_span::DUMMY_SP;🔒use rustc_span::Span;🔒use rustc_span::Symbol;🔒use super::AllocId;🔒use super::AllocRange;🔒use super::ConstAllocation;🔒use super::Pointer;🔒use super::Scalar;🔒use crate::diagnostics;🔒use crate::mir::interpret::CtfeProvenance;🔒use crate::mir::ConstAlloc;🔒use crate::mir::ConstValue;🔒use crate::ty;🔒use crate::ty::Ty;🔒use crate::ty::TyCtxt;🔒use crate::ty::ValTree;🔒use crate::ty::layout;🔒use crate::ty::tls;🔒
Structs§
- BadBytes
Access - Details of an access to uninitialized bytes / bad pointer bytes where it is not allowed.
- Guard 🔒
- Guard type that panics on drop.
- Interp
Error Backtrace - Interp
Error Info - 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. - Interp
Error 🔒Info Inner - Interp
Result - The result type used by the interpreter. This is a newtype around
Resultto block access to operations likeok()that discard UB errors. - Misalignment
- Information about a misaligned pointer.
- Reported
Error Info
Enums§
- Check
Align Msg - Details of which pointer is not aligned.
- Check
InAlloc Msg - Details of why a pointer had to be in-bounds.
- Error
Handled - Interp
Error Kind - Invalid
Meta Kind - Invalid
Program Info - 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.
- Resource
Exhaustion Info - Error information for when the program exhausted the resources granted to it by the interpreter.
- Undefined
Behavior Info - Error information for when the program caused Undefined Behavior.
- Unsupported
OpInfo - 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.
- ValTree
Creation Error - An error type for the
const_to_valtreequery. Some error should be reported with a “use-site span”, which means the query cannot emit the error, so those errors are represented as dedicated variants here.
Traits§
- Machine
Stop Type - A trait for machine-specific errors (or other “machine stop” conditions).