From 92d47dbb2993d9ce7c6f83a387b1674535c76bb3 Mon Sep 17 00:00:00 2001 From: blyxyas Date: Fri, 18 Aug 2023 20:02:40 +0200 Subject: [PATCH] Add `emitting_lints` link to `Writing tests` and remove that `FIXME` --- book/src/development/writing_tests.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/book/src/development/writing_tests.md b/book/src/development/writing_tests.md index 7cb530a3bb9..8937e0d8e94 100644 --- a/book/src/development/writing_tests.md +++ b/book/src/development/writing_tests.md @@ -94,7 +94,6 @@ As our `foo_functions` lint is tested, the output would look something like this ``` failures: - ---- compile_test stdout ---- normalized stderr: error: function called "foo" @@ -104,19 +103,16 @@ LL | pub fn foo(&self) {} | ^^^ | = note: `-D clippy::foo-functions` implied by `-D warnings` - error: function called "foo" --> $DIR/foo_functions.rs:13:8 | LL | fn foo(&self) {} | ^^^ - error: function called "foo" --> $DIR/foo_functions.rs:19:4 | LL | fn foo() {} | ^^^ - error: aborting due to 3 previous errors ``` @@ -202,8 +198,7 @@ Should `span_lint_and_sugg` be used to generate a suggestion, but not all suggestions lead to valid code, you can use the `//@no-rustfix` comment on top of the test file, to not run `rustfix` on that file. -We'll talk about suggestions more in depth in a later chapter. - +We'll talk about suggestions more in depth in a [later chapter](emitting_lints.md). Use `cargo bless` to automatically generate the `.fixed` file after running the tests.