about summary refs log tree commit diff
path: root/src/doc/rustc-dev-guide
diff options
context:
space:
mode:
authorSébastien Duquette <ekse.0x@gmail.com>2018-08-23 00:23:03 -0400
committerWho? Me?! <mark-i-m@users.noreply.github.com>2018-08-23 21:56:35 -0500
commit88d9da22c781664cf785c06489813278a95ebd3a (patch)
tree3850c0ac05d4c01e614dc15137afb5041891318b /src/doc/rustc-dev-guide
parent6ebc0cd09bcc3f9e5fa76ba7de689f3914a444d1 (diff)
downloadrust-88d9da22c781664cf785c06489813278a95ebd3a.tar.gz
rust-88d9da22c781664cf785c06489813278a95ebd3a.zip
Fix lines over 80 columns.
Diffstat (limited to 'src/doc/rustc-dev-guide')
-rw-r--r--src/doc/rustc-dev-guide/src/diag.md6
-rw-r--r--src/doc/rustc-dev-guide/src/the-parser.md7
2 files changed, 7 insertions, 6 deletions
diff --git a/src/doc/rustc-dev-guide/src/diag.md b/src/doc/rustc-dev-guide/src/diag.md
index 3d9a6fc37e9..b30ec2ecafc 100644
--- a/src/doc/rustc-dev-guide/src/diag.md
+++ b/src/doc/rustc-dev-guide/src/diag.md
@@ -11,9 +11,9 @@ HIR and MIR, allowing for more informative error reporting.
 
 [span]: https://doc.rust-lang.org/nightly/nightly-rustc/syntax/source_map/struct.Span.html
 
-A `Span` can be looked up in a [`SourceMap`][sourcemap] to get a "snippet" useful
-for displaying errors with [`span_to_snippet`][sptosnip] and other similar
-methods on the `SourceMap`.
+A `Span` can be looked up in a [`SourceMap`][sourcemap] to get a "snippet"
+useful for displaying errors with [`span_to_snippet`][sptosnip] and other
+similar methods on the `SourceMap`.
 
 [sourcemap]: https://doc.rust-lang.org/nightly/nightly-rustc/syntax/source_map/struct.SourceMap.html
 [sptosnip]: https://doc.rust-lang.org/nightly/nightly-rustc/syntax/source_map/struct.SourceMap.html#method.span_to_snippet
diff --git a/src/doc/rustc-dev-guide/src/the-parser.md b/src/doc/rustc-dev-guide/src/the-parser.md
index 62b43c0eee9..ac902d91547 100644
--- a/src/doc/rustc-dev-guide/src/the-parser.md
+++ b/src/doc/rustc-dev-guide/src/the-parser.md
@@ -23,9 +23,10 @@ The `syntax` crate contains several main players,
   nodes.
 
 The main entrypoint to the parser is via the various `parse_*` functions in the
-[parser module]. They let you do things like turn a [`SourceFile`][sourcefile] (e.g.
-the source in a single file) into a token stream, create a parser from the
-token stream, and then execute the parser to get a `Crate` (the root AST node).
+[parser module]. They let you do things like turn a [`SourceFile`][sourcefile]
+(e.g. the source in a single file) into a token stream, create a parser from
+the token stream, and then execute the parser to get a `Crate` (the root AST
+node).
 
 To minimise the amount of copying that is done, both the `StringReader` and
 `Parser` have lifetimes which bind them to the parent `ParseSess`. This contains