Skip to content

Commit

Permalink
fix some more typos
Browse files Browse the repository at this point in the history
  • Loading branch information
nikomatsakis committed Sep 7, 2018
1 parent 4d9f2cc commit f3b63b4
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions src/how-to-build-and-run.md
Original file line number Diff line number Diff line change
Expand Up @@ -201,13 +201,14 @@ The sequence of commands you want is as follows:
- Subsequent builds: `./x.py build -i --stage 1 src/libstd --keep-stage 1`
- Note that we added the `--keep-stage 1` flag here

The effect of `--keep-stage1` is that we just *assume* that the old
The effect of `--keep-stage 1` is that we just *assume* that the old
standard library can be re-used. If you are editing the compiler, this
is almost always true: you haven't changed the standard library, after
all. But sometimes, it's not true: for example, if you are editing
the "metadata" part of the compiler, which controls how the compiler
encodes types and other states into the `rlib` files, or if you are editing
things that wind up in the metadata (such as the definition of the MIR).
encodes types and other states into the `rlib` files, or if you are
editing things that wind up in the metadata (such as the definition of
the MIR).

**The TL;DR is that you might get weird behavior from a compile when
using `--keep-stage 1`** -- for example, strange [ICEs](appendix/glossary.html) or other
Expand Down

0 comments on commit f3b63b4

Please sign in to comment.