summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFelix S. Klock II <pnkfelix@pnkfx.org>2018-05-22 15:05:02 +0200
committerFelix S. Klock II <pnkfelix@pnkfx.org>2018-05-29 23:02:40 +0200
commita4a5fa293453c4ff9339f11c47eb7262925f7c12 (patch)
tree0a1fa97fd98ba07b6162d03ccc69908ff4d50c4a
parentreview feedback: fix indentation of pattern candidates to match code elsewher... (diff)
downloadgrust-a4a5fa293453c4ff9339f11c47eb7262925f7c12.tar.gz
grust-a4a5fa293453c4ff9339f11c47eb7262925f7c12.tar.bz2
grust-a4a5fa293453c4ff9339f11c47eb7262925f7c12.tar.xz
Review feedback: update fixme comment to reflect reality.
-rw-r--r--src/librustc_mir/interpret/step.rs5
1 files changed, 2 insertions, 3 deletions
diff --git a/src/librustc_mir/interpret/step.rs b/src/librustc_mir/interpret/step.rs
index b9edd2c07f..ab15278219 100644
--- a/src/librustc_mir/interpret/step.rs
+++ b/src/librustc_mir/interpret/step.rs
@@ -79,9 +79,8 @@ impl<'a, 'mir, 'tcx, M: Machine<'mir, 'tcx>> EvalContext<'a, 'mir, 'tcx, M> {
79 self.deallocate_local(old_val)?; 79 self.deallocate_local(old_val)?;
80 } 80 }
81 81
82 // FIXME: is there some dynamic semantics we should attach to 82 // No dynamic semantics attached to `ReadForMatch`; MIR
83 // these? Or am I correct in thinking that the inerpreter 83 // interpreter is solely intended for borrowck'ed code.
84 // is solely intended for borrowck'ed code?
85 ReadForMatch(..) => {} 84 ReadForMatch(..) => {}
86 85
87 // Validity checks. 86 // Validity checks.