Skip to content

Commit 9263df7

Browse files
spastorinomark-i-m
authored andcommitted
Fix line lengths
1 parent 8a93493 commit 9263df7

File tree

2 files changed

+12
-12
lines changed

2 files changed

+12
-12
lines changed

src/bug-fix-procedure.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -289,13 +289,13 @@ self.tcx.sess.add_lint(lint::builtin::OVERLAPPING_INHERENT_IMPLS,
289289
msg);
290290
```
291291

292-
We want to convert this into an error. In some cases, there may be an existing
293-
error for this scenario. In others, we will need to allocate a fresh diagnostic
294-
code.
295-
[Instructions for allocating a fresh diagnostic code can be found here.](diagnostics/diagnostic-codes.html)
296-
You may want to mention in the extended description that the compiler behavior
297-
changed on this point, and include a reference to the tracking issue for the
298-
change.
292+
We want to convert this into an error. In some cases, there may be an
293+
existing error for this scenario. In others, we will need to allocate a
294+
fresh diagnostic code. [Instructions for allocating a fresh diagnostic
295+
code can be found here.](diagnostics/diagnostic-codes.html) You may want
296+
to mention in the extended description that the compiler behavior
297+
changed on this point, and include a reference to the tracking issue for
298+
the change.
299299

300300
Let's say that we've adopted `E0592` as our code. Then we can change the
301301
`add_lint()` call above to something like:

src/tests/intro.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
# The compiler testing framework
22

3-
The Rust project runs a wide variety of different tests, orchestrated
4-
by the build system (`x.py test`). The main test harness for testing
5-
the compiler itself is a tool called compiletest (located in the
3+
The Rust project runs a wide variety of different tests, orchestrated by
4+
the build system (`x.py test`). The main test harness for testing the
5+
compiler itself is a tool called compiletest (located in the
66
[`src/tools/compiletest`] directory). This section gives a brief
77
overview of how the testing framework is setup, and then gets into some
8-
of the details on [how to run tests](./running.html) as well as
9-
[how to add new tests](./adding.html).
8+
of the details on [how to run tests](./running.html) as well as [how to
9+
add new tests](./adding.html).
1010

1111
[`src/tools/compiletest`]: https://github.com/rust-lang/rust/tree/master/src/tools/compiletest
1212

0 commit comments

Comments
 (0)