diff options
| author | Who? Me?! <mark-i-m@users.noreply.github.com> | 2018-01-01 13:17:25 -0600 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-01-01 13:17:25 -0600 |
| commit | 05cbe6d7db043c18b99a306ace7bbf3ff59c82e8 (patch) | |
| tree | e7020f95fc454a93085dd74d531dfc731bc465a6 | |
| parent | 5deba220d4c42b5313d7e71731ce5e8698866684 (diff) | |
| download | rust-05cbe6d7db043c18b99a306ace7bbf3ff59c82e8.tar.gz rust-05cbe6d7db043c18b99a306ace7bbf3ff59c82e8.zip | |
Fix typo
| -rw-r--r-- | src/librustc/mir/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/librustc/mir/README.md b/src/librustc/mir/README.md index fb0c7ce1df2..cac86be0fcb 100644 --- a/src/librustc/mir/README.md +++ b/src/librustc/mir/README.md @@ -59,7 +59,7 @@ ensure that, before the MIR at a particular phase in the processing pipeline is stolen, anyone who may want to read from it has already done so. Concretely, this means that if you have some query `foo(D)` that wants to access the result of `mir_const(D)` or -`mir_validated(D)`, you need to have the successor pass either "force" +`mir_validated(D)`, you need to have the successor pass "force" `foo(D)` using `ty::queries::foo::force(...)`. This will force a query to execute even though you don't directly require its result. |