I've found it weird that cargo will look first in
~/.cargo/bin for custom subcommands. If I run
/my/path/to/a/toolchain/install/bin/cargo clippy, I would expect, I think, for
/my/path/to/a/toolchain/install/bin/cargo-clippy to be higher priority than
~/.cargo/bin/cargo-clippy, which will invoke whatever the default toolchain managed by rustup is.
I also don't love that
~/.cargo/bin is higher priority than PATH - it makes it impossible to override the subcommands installed in
Is this behavior intentional?