mirror
/
rustc-dev-guide
mirror of https://github.com/rust-lang/rustc-dev-guide.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix minor typos

This commit is contained in:
Who? Me?! 2018-01-30 11:38:37 -06:00 committed by GitHub
parent 066a32c961
commit 150db58b61
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/incremental-compilation.md
View File

@ -64,7 +64,7 @@ Try-mark-green works as follows:
- If there is a saved result, then we load the `reads(Q)` vector from the - If there is a saved result, then we load the `reads(Q)` vector from the
query DAG. The "reads" is the set of queries that Q executed during query DAG. The "reads" is the set of queries that Q executed during
its execution. its execution.
- For each query R that in `reads(Q)`, we recursively demand the color - For each query R in `reads(Q)`, we recursively demand the color
of R using try-mark-green. of R using try-mark-green.
- Note: it is important that we visit each node in `reads(Q)` in same order - Note: it is important that we visit each node in `reads(Q)` in same order
as they occurred in the original compilation. See [the section on the query DAG below](#dag). as they occurred in the original compilation. See [the section on the query DAG below](#dag).
@ -84,7 +84,7 @@ The query DAG code is stored in
by instrumenting the query execution. by instrumenting the query execution.
One key point is that the query DAG also tracks ordering; that is, for One key point is that the query DAG also tracks ordering; that is, for
each query Q, we noy only track the queries that Q reads, we track the each query Q, we not only track the queries that Q reads, we track the
**order** in which they were read. This allows try-mark-green to walk **order** in which they were read. This allows try-mark-green to walk
those queries back in the same order. This is important because once a subquery comes back as red, those queries back in the same order. This is important because once a subquery comes back as red,
we can no longer be sure that Q will continue along the same path as before. we can no longer be sure that Q will continue along the same path as before.