Explain why we do not allow const_to_valtree to read from statics

1 files changed, 6 insertions, 1 deletions

diff --git a/compiler/rustc_mir/src/const_eval/mod.rs b/compiler/rustc_mir/src/const_eval/mod.rs
index ca165f2c8cb..4086c18c3d2 100644
--- a/compiler/rustc_mir/src/const_eval/mod.rs
+++ b/compiler/rustc_mir/src/const_eval/mod.rs
@@ -44,7 +44,12 @@ pub(crate) fn const_to_valtree<'tcx>(
     param_env: ty::ParamEnv<'tcx>,
     raw: ConstAlloc<'tcx>,
 ) -> Option<ty::ValTree<'tcx>> {
-    let ecx = mk_eval_cx(tcx, DUMMY_SP, param_env, false);
+    let ecx = mk_eval_cx(
+        tcx, DUMMY_SP, param_env,
+        // It is absolutely crucial for soundness that
+        // we do not read from static items or other mutable memory.
+        false,
+    );
     let place = ecx.raw_const_to_mplace(raw).unwrap();
     const_to_valtree_inner(&ecx, &place)
 }