Skip to content

Commit 4867fa7

Browse files
Link to Miri engine in rustc guide, not Miri project
1 parent 9652c80 commit 4867fa7

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

posts/inside-rust/2019-11-23-const-if-match.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -105,14 +105,14 @@ us know if something goes horribly wrong.
105105

106106
## What took you so long?
107107

108-
[Miri], which rust uses under the hood for compile-time function evaluation,
109-
has been capable of this for a while now. However, rust needs to statically
110-
guarantee certain properties about variables in a `const`, such as whether
111-
they allow for interior mutability or whether they have a `Drop`
112-
implementation that needs to be called. For example, we must reject the
108+
[The Miri engine][miri], which rust uses under the hood for compile-time
109+
function evaluation, has been capable of this for a while now. However, rust
110+
needs to statically guarantee certain properties about variables in a `const`,
111+
such as whether they allow for interior mutability or whether they have a
112+
`Drop` implementation that needs to be called. For example, we must reject the
113113
following code since it would result in a `const` being mutable at runtime!
114114

115-
[Miri]: https://github.com/rust-lang/miri
115+
[miri]: https://rust-lang.github.io/rustc-guide/miri.html
116116

117117
```rust
118118
const CELL: &std::cell::Cell<i32> = &std::cell::Cell::new(42); // Not allowed...

0 commit comments

Comments
 (0)