bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity

Rename const eval queries to reflect the validation changes

Browse source
This commit is contained in:
Oliver Scherer 2020-08-10 15:11:40 +02:00
parent 40c2087eb5
commit 69a6be73e6
6 changed files with 20 additions and 27 deletions
Download patch file Download diff file Expand all files Collapse all files

19
compiler/rustc_middle/src/query/mod.rs
View file

@ -707,13 +707,8 @@ rustc_queries! {
}
Other {
/// Evaluates a constant without running sanity checks.
///
/// **Do not use this** outside const eval. Const eval uses this to break query cycles
/// during validation. Please add a comment to every use site explaining why using
/// `const_eval_validated` isn't sufficient. The returned constant also isn't in a suitable
/// form to be used outside of const eval.
query const_eval_raw(key: ty::ParamEnvAnd<'tcx, GlobalId<'tcx>>)
/// Evaluates a constant and returns the computed allocation.
query const_eval(key: ty::ParamEnvAnd<'tcx, GlobalId<'tcx>>)
-> ConstEvalRawResult<'tcx> {
desc { |tcx|
"const-evaluating `{}`",
@ -721,15 +716,13 @@ rustc_queries! {
}
}
/// Results of evaluating const items or constants embedded in
/// other items (such as enum variant explicit discriminants).
///
/// In contrast to `const_eval_raw` this performs some validation on the constant, and
/// returns a proper constant that is usable by the rest of the compiler.
/// Evaluates const items or anonymous constants
/// (such as enum variant explicit discriminants or array lengths)
/// into a representation suitable for the type system and const generics.
///
/// **Do not use this** directly, use one of the following wrappers: `tcx.const_eval_poly`,
/// `tcx.const_eval_resolve`, `tcx.const_eval_instance`, or `tcx.const_eval_global_id`.
query const_eval_validated(key: ty::ParamEnvAnd<'tcx, GlobalId<'tcx>>)
query const_eval_for_ty(key: ty::ParamEnvAnd<'tcx, GlobalId<'tcx>>)
-> ConstEvalResult<'tcx> {
desc { |tcx|
"const-evaluating + checking `{}`",