about summary refs log tree commit diff
diff options
context:
space:
mode:
authorRalf Jung <post@ralfj.de>2023-03-20 19:36:01 +0100
committerRalf Jung <post@ralfj.de>2023-03-20 19:36:01 +0100
commit5058cc8e62f1557f684d90ff0dde7cedc6c5d529 (patch)
treead979c913c95556ff1b55e066f7b3cc39fa736a7
parent13b7aa4d7faafbed78d195c27f6868f6bd90c2f8 (diff)
downloadrust-5058cc8e62f1557f684d90ff0dde7cedc6c5d529.tar.gz
rust-5058cc8e62f1557f684d90ff0dde7cedc6c5d529.zip
not *all* retags might be explicit in Runtime MIR
-rw-r--r--compiler/rustc_middle/src/mir/syntax.rs3
1 files changed, 2 insertions, 1 deletions
diff --git a/compiler/rustc_middle/src/mir/syntax.rs b/compiler/rustc_middle/src/mir/syntax.rs
index b16b6616415..f25577de6a4 100644
--- a/compiler/rustc_middle/src/mir/syntax.rs
+++ b/compiler/rustc_middle/src/mir/syntax.rs
@@ -78,7 +78,8 @@ pub enum MirPhase {
     ///    MIR, this is UB.
     ///  - Retags: If `-Zmir-emit-retag` is enabled, analysis MIR has "implicit" retags in the same way
     ///    that Rust itself has them. Where exactly these are is generally subject to change, and so we
-    ///    don't document this here. Runtime MIR has all retags explicit.
+    ///    don't document this here. Runtime MIR has most retags explicit (though implicit retags
+    ///    can still occur at `Rvalue::{Ref,AddrOf}`).
     ///  - Generator bodies: In analysis MIR, locals may actually be behind a pointer that user code has
     ///    access to. This occurs in generator bodies. Such locals do not behave like other locals,
     ///    because they eg may be aliased in surprising ways. Runtime MIR has no such special locals -