Fix a comment that only made sense in the context of a dataflow based mutability...

diff --git a/src/test/ui/consts/const-mut-refs/mut_ref_in_final.rs b/src/test/ui/consts/const-mut-refs/mut_ref_in_final.rs
index c85acd3b849873fad91d1713a92a465aed925647..98960ec6c6e8ad94bbd74a3537edc99e18a546c9 100644 (file)
--- a/src/test/ui/consts/const-mut-refs/mut_ref_in_final.rs
+++ b/src/test/ui/consts/const-mut-refs/mut_ref_in_final.rs
@@ -9,9 +9,8 @@
 // as that would be an enormous footgun in oli-obk's opinion.
 const B: *mut i32 = &mut 4; //~ ERROR mutable references are not allowed
 
-// Could be ok, but the same analysis that prevents the mutable one above will also bail out here
-// Using a block with some complex content, because just `&45` would get promoted,
-// which is not what we want to test here.
+// Ok, because no references to mutable data exist here, since the `{}` moves
+// its value and then takes a reference to that.
 const C: *const i32 = &{
     let mut x = 42;
     x += 3;