From f2b49d978cbd24e35d4a10fcad9f5951ef4e2867 Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Thu, 6 Jun 2019 11:47:52 +0200 Subject: [PATCH] avoid 'const-context' terminology --- src/librustc_mir/transform/qualify_consts.rs | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/librustc_mir/transform/qualify_consts.rs b/src/librustc_mir/transform/qualify_consts.rs index 53f3f226b24bc..ca676cf194553 100644 --- a/src/librustc_mir/transform/qualify_consts.rs +++ b/src/librustc_mir/transform/qualify_consts.rs @@ -48,9 +48,8 @@ enum Mode { } impl Mode { - /// Determine whether we are running in "const context". "const context" refers - /// to code type-checked according to the rules of the "const type system": - /// the bodies of const/static items and `const fn`. + /// Determine whether we have to do full const-checking because syntactically, we + /// are required to be "const". #[inline] fn requires_const_checking(self) -> bool { self != Mode::NonConstFn