You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a lot of discussion with reddit and friends, it seems that deprecating rustup install and rustup uninstall would have consequences I'd not considered (printed books) and as such it'd be unpleasantly surprising for new users to be told the book they bought was wrong.
As such, we should demote the deprecation warning code from warn!() to verbose!() and make it clear that the reason for the message is that until true alias support is added, these may not function quite as the toolchain XXX commands would.
Long-term we want to replace the deprecated subcommands with true aliases so that this can't be a problem again in the future.
The text was updated successfully, but these errors were encountered:
The printed book use case is largely handled by just replacing the existing code with a message that says to use rustup toolchain install instead, isn't it? That code would be simple enough that it wouldn't be buggy, nor would it be a duplication of the rustup toolchain install code.
We decided that the deprecation messages ought to be verbose
messages (i.e. only in --verbose mode) rather than warnings.
Fixes: rust-lang#2149
Signed-off-by: Daniel Silverstone <[email protected]>
After a lot of discussion with reddit and friends, it seems that deprecating
rustup install
andrustup uninstall
would have consequences I'd not considered (printed books) and as such it'd be unpleasantly surprising for new users to be told the book they bought was wrong.As such, we should demote the deprecation warning code from
warn!()
toverbose!()
and make it clear that the reason for the message is that until true alias support is added, these may not function quite as thetoolchain XXX
commands would.Long-term we want to replace the deprecated subcommands with true aliases so that this can't be a problem again in the future.
The text was updated successfully, but these errors were encountered: