Module rustc_const_eval::interpret::validity
source · [−]Expand description
Check the validity invariant of a given value, and tell the user
where in the value it got violated.
In const context, this goes even further and tries to approximate const safety.
That’s useful because it means other passes (e.g. promotion) can rely on consts
to be const-safe.
Macros
If $e throws an error matching the pattern, throw a validation failure.
Other errors are passed back to the caller, unchanged – and if they reach the root of
the visitor, we make sure only validation errors and
InvalidProgram errors are left.
This lets you use the patterns as a kind of validation list, asserting which errors
can possibly happen:Structs
State for tracking recursive validation of references
Enums
Extra things to check for during validation of CTFE results.
We want to show a nice path to the invalid field for diagnostics,
but avoid string operations in the happy case where no error happens.
So we track a
Vec<PathElem> where PathElem contains all the data we
need to later print something for the user.Functions
Format a path