Skip to content
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

Merged
merged 1 commit into from
May 5, 2017

Conversation

alexcrichton
Copy link
Member

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

@rust-highfive
Copy link
Collaborator

r? @eddyb

(rust_highfive has picked a reviewer for you, use r? to override)

@kennytm
Copy link
Member

kennytm commented May 4, 2017

so... what about #41743 ("Firefox requires -Zdebug-macros")?

@alexcrichton
Copy link
Member Author

That's a feature that should be stabilized in time, not block this.

@Mark-Simulacrum
Copy link
Member

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.

[00:05:47] error: unused import: `early_warn`
[00:05:47]     --> /checkout/src/librustc/session/config.rs:1664:32
[00:05:47]      |
[00:05:47] 1664 |     use session::{early_error, early_warn};
[00:05:47]      |                                ^^^^^^^^^^
[00:05:47]      |
[00:05:47]      = note: #[deny(unused_imports)] implied by #[deny(warnings)]
[00:05:47] note: lint level defined here
[00:05:47]     --> /checkout/src/librustc/lib.rs:24:9
[00:05:47]      |
[00:05:47] 24   | #![deny(warnings)]
[00:05:47]      |         ^^^^^^^^
[00:05:47] 
[00:05:48] error: aborting due to previous error

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
@alexcrichton
Copy link
Member Author

@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.

@alexcrichton alexcrichton added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label May 4, 2017
@eddyb
Copy link
Member

eddyb commented May 4, 2017

@bors r+

@bors
Copy link
Contributor

bors commented May 4, 2017

📌 Commit ccbcc72 has been approved by eddyb

frewsxcv added a commit to frewsxcv/rust that referenced this pull request May 5, 2017
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
@bors
Copy link
Contributor

bors commented May 5, 2017

⌛ Testing commit ccbcc72 with merge 50b9858...

bors added a commit that referenced this pull request May 5, 2017
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
@bors
Copy link
Contributor

bors commented May 5, 2017

☀️ Test successful - status-appveyor, status-travis
Approved by: eddyb
Pushing 50b9858 to master...

@bors bors merged commit ccbcc72 into rust-lang:master May 5, 2017
bors added a commit that referenced this pull request May 9, 2017
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.
@jsgf
Copy link
Contributor

jsgf commented May 10, 2017

I think this is a mistake: https://internals.rust-lang.org/t/disabling-z-for-stable-builds-is-a-mistake/5221

@alexcrichton alexcrichton deleted the unstable-flags branch June 14, 2017 18:40
SimonSapin added a commit to servo/skia that referenced this pull request Jun 16, 2017
@K4sum1
Copy link

K4sum1 commented Apr 2, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Tracking issue for accepting unstable flags in stable compilers
8 participants