From 9c853c9a237da57bfb88cf450aaa413154bc4d7a Mon Sep 17 00:00:00 2001 From: Santiago Pastorino Date: Mon, 16 Mar 2020 18:51:29 -0300 Subject: [PATCH] Fix line lengths --- src/bug-fix-procedure.md | 14 +++++++------- src/tests/intro.md | 10 +++++----- 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/src/bug-fix-procedure.md b/src/bug-fix-procedure.md index 9ad57be9..9c711ae1 100644 --- a/src/bug-fix-procedure.md +++ b/src/bug-fix-procedure.md @@ -289,13 +289,13 @@ self.tcx.sess.add_lint(lint::builtin::OVERLAPPING_INHERENT_IMPLS, msg); ``` -We want to convert this into an error. In some cases, there may be an existing -error for this scenario. In others, we will need to allocate a fresh diagnostic -code. -[Instructions for allocating a fresh diagnostic code can be found here.](diagnostics/diagnostic-codes.html) -You may want to mention in the extended description that the compiler behavior -changed on this point, and include a reference to the tracking issue for the -change. +We want to convert this into an error. In some cases, there may be an +existing error for this scenario. In others, we will need to allocate a +fresh diagnostic code. [Instructions for allocating a fresh diagnostic +code can be found here.](diagnostics/diagnostic-codes.html) You may want +to mention in the extended description that the compiler behavior +changed on this point, and include a reference to the tracking issue for +the change. Let's say that we've adopted `E0592` as our code. Then we can change the `add_lint()` call above to something like: diff --git a/src/tests/intro.md b/src/tests/intro.md index cdb22a19..b70a23a6 100644 --- a/src/tests/intro.md +++ b/src/tests/intro.md @@ -1,12 +1,12 @@ # The compiler testing framework -The Rust project runs a wide variety of different tests, orchestrated -by the build system (`x.py test`). The main test harness for testing -the compiler itself is a tool called compiletest (located in the +The Rust project runs a wide variety of different tests, orchestrated by +the build system (`x.py test`). The main test harness for testing the +compiler itself is a tool called compiletest (located in the [`src/tools/compiletest`] directory). This section gives a brief overview of how the testing framework is setup, and then gets into some -of the details on [how to run tests](./running.html) as well as -[how to add new tests](./adding.html). +of the details on [how to run tests](./running.html) as well as [how to +add new tests](./adding.html). [`src/tools/compiletest`]: https://github.com/rust-lang/rust/tree/master/src/tools/compiletest