Add usage instructions of cargo clippy build

Author: blyxyas

README.md

@@ -88,6 +88,13 @@ Now you can run Clippy by invoking the following command:
 cargo clippy
 ```
 
+You can also test or build your project with Clippy lints as add-on with this command:
+
+```terminal
+cargo clippy build
+cargo clippy test
+```
+
 #### Automatically applying Clippy suggestions
 
 Clippy can automatically apply some lint suggestions, just like the compiler. Note that `--fix` implies

book/src/continuous_integration/README.md

@@ -16,3 +16,11 @@ your crate for maximum compatibility. E.g. if your crate is compiled with the
 
 This chapter will give an overview on how to use Clippy on different popular CI
 providers.
+
+## CI Time optimization
+
+You can optimize time in your CI by running `cargo clippy test`, this will test your application at the same time as
+it's linted. If Clippy doesn't report anything (or only has warnings), you will be saving precious CI time, as
+there's no need to rebuild your application.
+
+So, compilation time is halved compared to running `cargo clippy` and THEN `cargo test`.

book/src/usage.md

@@ -16,6 +16,16 @@ just run
 cargo clippy
 ```
 
+## Running build/test at the same time as Clippy
+
+You can also emit binaries and test your project with Clippy enabled! Reducing your compilation times as there's no
+need to recompile.
+
+```bash
+cargo clippy test
+cargo clippy build
+```
+
 ### Lint configuration
 
 The above command will run the default set of lints, which are included in the

src/main.rs

@@ -77,10 +77,7 @@ impl ClippyCmd {
                 },
                 "--fix" => {
                     if cargo_subcommand != "check" {
-                        eprintln!(
-                            "Running `cargo clippy {}` is not available with the --fix flag",
-                            cargo_subcommand
-                        );
+                        eprintln!("Running `cargo clippy {cargo_subcommand}` is not available with the --fix flag");
                         process::exit(1) // Same code as `--explain` encountering an unknown lint
                     }
                     cargo_subcommand = "fix";