Suggested `cargo fix` command does not specify `+nightly`

[Muscraft]

Problem

When running cargo with cargo +nightly check the suggested cargo fix command does not include +nightly i.e.

warning: `scratch` (bin "scratch") generated 1 warning (run `cargo fix --bin "scratch"` to apply 1 suggestion)

It seems like a misstep to be showing the "command to run" but not having it include +nightly.

Steps

1. Have a nightly version of cargo installed
2. Run cargo new scratch && cd scratch
3. Edit the main function to throw a machine-fixable warning

fn main() {
    let test = 0;
}

4. Run cargo +nightly check
5. Observe the warning line

Possible Solution(s)

• No Change
• Just refer to the command, not saying how to run it
• Try to detect the use of rustup and which toolchain is being used and specify the + (which might be redundant with rustup-toolchain.toml)
• Do a modified version of cargo test: to apply 1 suggestion pass '...' to cargo-fix

Notes

No response

Version

cargo 1.68.0-nightly (8c460b223 2023-01-04)
release: 1.68.0-nightly
commit-hash: 8c460b2237a6359a7e3335890db8da049bdd62fc
commit-date: 2023-01-04
host: aarch64-apple-darwin
libgit2: 1.5.0 (sys:0.15.0 vendored)
libcurl: 7.85.0 (sys:0.4.59+curl-7.86.0 system ssl:(SecureTransport) LibreSSL/3.3.6)
os: Mac OS 13.1.0 [64-bit]

[ehuss]

It might be difficult to reliably suggestion a succinct + shorthand. I think Cargo can only really determine the full toolchain name, like +nightly-2020-03-01-x86_64-apple-darwin. My expectation is that most users are not using shorthand overrides in their normal operation (instead using the default, directory overrides, or rust-toolchain.toml), in which case the shorthand would usually be redundant.

[weihanglo]

Perhaps I should have posted this to a new issue.

After running cargo clippy -- -W clippy::doc_markdown, Cargo suggests cargo clippy --fix --lib -p cargo, which I believe should be cargo clippy --fix --lib -p cargo -- -W clippy::doc_markdown. Trailing varargs may also have to be included?