rami3l

Following the long-term goal of eliminating implicit installation (https://github.com/rust-lang/rustup/issues/3635), I think the best thing to do here is to add a warning.

Ah, I do remember the days when installing Rust took a long time to finish: https://github.com/rust-lang/rustup/pull/1876 (cc the original author, if I'm not mistaken, @rbtcollins)

Note: The tests are failing as expected. I'll first use these tests to see whether the feature is working, and then add omission indicators to the UI tests if everything...

> Is the intent to provide a one-time warning, or one-time warning per toolchain or something else? @wesleywiser We definitely don't want to spam you with warnings, but that will...

@ave9858 Thanks for filing this issue! Unfortunately I don't currently use Windows and I wonder how exactly winget expect `DisplayVersion` to change, and I'm curious about how we would be...

@ave9858 [A new beta release is available](https://internals.rust-lang.org/t/seeking-beta-testers-for-rustup-v1-27-1/20730), would you mind trying it out?

> Looks like a downgrade triggered by removing the `RUSTUP_UPDATE_ROOT` env var will set the version correctly. Tested by installing 1.26.0, updating to 1.27.0 (display version not updated), updating to...

> Maybe a stupid idea but: Instead of trying to associate version numbers or any of that, couldn't at least a subset of these situations be solved using the hashes...

I have encountered a similar problem once when running `brew upgrade` and another time when running `albemic revision --autogenerate`. Looks like any subprocess that is able to run for a...

Mitigated by https://github.com/Homebrew/homebrew-core/pull/177983 if you're using a `brew`-managed `rustup` installation. Please note that now you need to add `$(brew --prefix rustup)/bin` to PATH manually to reach to the `rustup`-installed toolchain....