diff options
| author | kennytm <kennytm@gmail.com> | 2018-01-03 16:57:56 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-01-03 16:57:56 +0800 |
| commit | dd0b70e3fe80d6c48b6522dda6fe8809cea0405a (patch) | |
| tree | 623c1c560f106ce4ba13e0f0e86ec8eb7a193950 | |
| parent | f7932ef1d5059058fa8b01b7df26b628f613d5ee (diff) | |
| parent | 05cbe6d7db043c18b99a306ace7bbf3ff59c82e8 (diff) | |
Rollup merge of #47107 - mark-i-m:patch-1, r=steveklabnik
Fix typo I am assuming that there was once something else you could do and somebody forgot to remove "either". Is that correct?
| -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. |