Skip to content

Commit 37b7452

Browse files
pnkfelixRalfJung
andauthored
Apply RalfJ's suggestions from code review
Co-authored-by: Ralf Jung <post@ralfj.de>
1 parent 5ad3ff0 commit 37b7452

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

posts/2022-09-15-const-eval-safety-rule-revision.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ fine-grained checking for UB, it uses a much richer datatype for
105105
the values that are held in the abstract memory store.
106106

107107
(The aforementioned MIR interpreter is also the basis for [Miri][], a research
108-
tool that interprets both const and non-const Rust code, with a focus on
108+
tool that interprets *non-const* Rust code, with a focus on
109109
explicit detection of undefined behavior. The Miri developers are the primary
110110
contributors to the CTFE engine in the Rust compiler.)
111111

@@ -329,5 +329,6 @@ that the 1.64 stable release will not encounter any other surprises related to
329329
the aforementioned change to the const-eval machinery.
330330

331331
But fluke or not, the issue provided excellent motivation to spend some time
332-
exploring facets of Rust's const-eval architecture.
332+
exploring facets of Rust's const-eval architecture and the interpreter
333+
that underlies it.
333334
We hope you enjoyed reading this as much as we did writing it.

0 commit comments

Comments
 (0)