-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rustc: Forbid -Z
flags on stable/beta channels
#41751
Conversation
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
so... what about #41743 ("Firefox requires |
That's a feature that should be stabilized in time, not block this. |
Travis failed legitimately, I think. I'm somewhat concerned that we'd break Firefox's debugging process by landing this, though, especially with no current clear path forward for debug-macros.
|
First deprecated in rustc 1.8.0 the intention was to never allow `-Z` flags make their way to the stable channel (or unstable options). After a year of warnings we've seen one of the main use cases, `-Z no-trans`, stabilized as `cargo check`. Otherwise while other use cases remain the sentiment is that now's the time to start forbidding `-Z` by default on stable/beta. Closes rust-lang#31847
45ae0f4
to
ccbcc72
Compare
@Mark-Simulacrum we've been printing for over a year that this will become a warning, debugging with these features will continue to work on nightly, as is intended. |
@bors r+ |
📌 Commit ccbcc72 has been approved by |
rustc: Forbid `-Z` flags on stable/beta channels First deprecated in rustc 1.8.0 the intention was to never allow `-Z` flags make their way to the stable channel (or unstable options). After a year of warnings we've seen one of the main use cases, `-Z no-trans`, stabilized as `cargo check`. Otherwise while other use cases remain the sentiment is that now's the time to start forbidding `-Z` by default on stable/beta. Closes rust-lang#31847
rustc: Forbid `-Z` flags on stable/beta channels First deprecated in rustc 1.8.0 the intention was to never allow `-Z` flags make their way to the stable channel (or unstable options). After a year of warnings we've seen one of the main use cases, `-Z no-trans`, stabilized as `cargo check`. Otherwise while other use cases remain the sentiment is that now's the time to start forbidding `-Z` by default on stable/beta. Closes #31847
☀️ Test successful - status-appveyor, status-travis |
Bump cargo for rust-lang/cargo#4000 rust-lang/cargo#4000 recently landed, which fixes warnings about using `-Z` when `CARGO_INCREMENTAL` is set while running stable/beta builds. As #41751 has now landed, these warnings will turn to errors in the next release, so getting the cargo fix in place is necessary unless we want people confused about why they can no longer compile anything on stable/beta.
I think this is a mistake: https://internals.rust-lang.org/t/disabling-z-for-stable-builds-is-a-mistake/5221 |
It has been over 7 years can we have this reverted now? Or can rustup default nightly be made to actually work so I don't need to rename the nightly toolkit folder to stable? |
First deprecated in rustc 1.8.0 the intention was to never allow
-Z
flags maketheir way to the stable channel (or unstable options). After a year of warnings
we've seen one of the main use cases,
-Z no-trans
, stabilized ascargo check
. Otherwise while other use cases remain the sentiment is that now's thetime to start forbidding
-Z
by default on stable/beta.Closes #31847