renames EvalContext to InterpretCx in docs and comments.
This commit is contained in:
parent
630d5a4895
commit
892f7c430d
|
@ -344,7 +344,7 @@ impl<'tcx> AllocMap<'tcx> {
|
|||
}
|
||||
}
|
||||
|
||||
/// Returns `None` in case the `AllocId` is dangling. An `EvalContext` can still have a
|
||||
/// Returns `None` in case the `AllocId` is dangling. An `InterpretCx` can still have a
|
||||
/// local `Allocation` for that `AllocId`, but having such an `AllocId` in a constant is
|
||||
/// illegal and will likely ICE.
|
||||
/// This function exists to allow const eval to detect the difference between evaluation-
|
||||
|
|
|
@ -34,7 +34,7 @@ const STEPS_UNTIL_DETECTOR_ENABLED: isize = 1_000_000;
|
|||
/// Should be a power of two for performance reasons.
|
||||
const DETECTOR_SNAPSHOT_PERIOD: isize = 256;
|
||||
|
||||
/// The `EvalContext` is only meant to be used to do field and index projections into constants for
|
||||
/// The `InterpretCx` is only meant to be used to do field and index projections into constants for
|
||||
/// `simd_shuffle` and const patterns in match arms.
|
||||
///
|
||||
/// The function containing the `match` that is currently being analyzed may have generic bounds
|
||||
|
|
Loading…
Reference in New Issue