Make clippy happy

Signed-off-by: hi-rustin <[email protected]>

Author: 0xPoe

CONTRIBUTING.md

@@ -4,14 +4,12 @@
 2. Create your feature branch: `git checkout -b my-new-feature`
 3. Test it: `cargo test`
 4. Lint it: `cargo +beta clippy --all --all-targets -- -D warnings`
-
 > We use `cargo clippy` to ensure high-quality code and to enforce a set of best practices for Rust programming. However, not all lints provided by `cargo clippy` are relevant or applicable to our project.
 > We may choose to ignore some lints if they are unstable, experimental, or specific to our project.
 > If you are unsure about a lint, please ask us in the [rustup Discord channel](https://discord.com/channels/442252698964721669/463480252723888159).
-
-1. Commit your changes: `git commit -am 'Add some feature'`
-2. Push to the branch: `git push origin my-new-feature`
-3. Submit a pull request :D
+5. Commit your changes: `git commit -am 'Add some feature'`
+6. Push to the branch: `git push origin my-new-feature`
+7. Submit a pull request :D
 
 For developing on `rustup` itself, you may want to install into a temporary
 directory, with a series of commands similar to this:

tests/suite/cli_rustup.rs

@@ -583,7 +583,7 @@ fn recursive_cargo() {
             let cargo_bin_path = config.cargodir.join("bin");
             let cargo_subcommand = cargo_bin_path.join(format!("cargo-foo{}", EXE_SUFFIX));
             fs::create_dir_all(&cargo_bin_path).unwrap();
-            fs::copy(&real_mock_cargo, &cargo_subcommand).unwrap();
+            fs::copy(real_mock_cargo, cargo_subcommand).unwrap();
 
             // Verify the default behavior, which is currently broken on Windows.
             let args = &["cargo", "--recursive-cargo-subcommand"];