Repository navigation
do not complain about unstable target features on nightly - #163428
Conversation
|
The rustc-dev-guide subtree was changed. If your future PRs only touch the subtree, consider submitting them directly to rust-lang/rustc-dev-guide, which is where the document is primarily maintained (and has faster CI). |
|
rustbot has assigned @petrochenkov. Use Why was this reviewer chosen?The reviewer was selected based on:
|
| //@ rustc-env:RUSTC_BOOTSTRAP=1 | ||
|
|
||
| // Or force nightly rustc to pretend it is a stable rustc | ||
| //@ rustc-env:RUSTC_BOOTSTRAP=-1 |
There was a problem hiding this comment.
I don't know if rustc-env:RUSTC_BOOTSTRAP=1 ever makes sense in a ui test, but rustc-env:RUSTC_BOOTSTRAP=-1 definitely does not.
Cc @jieyouxu
There was a problem hiding this comment.
Yeah... This is #t-compiler > Testing stable vs nightly behavior in UI tests
There was a problem hiding this comment.
Okay so rustc-env:RUSTC_BOOTSTRAP=1 is also pointless. I'll remove the example then.
c646ae4 to
cc5a973
Compare
This comment has been minimized.
This comment has been minimized.
|
r=me after fixing tidy. |
|
Lol, tidy +rustfmt make it impossible to have an empty file. I guess I'm going to have to add a dummy function. |
032423d to
edc2f3b
Compare
|
@bors r=petrochenkov rollup |
This comment has been minimized.
This comment has been minimized.
|
❌ Commit edc2f3b has been unapproved due to PR CI failure. Reapprove it with |
edc2f3b to
8846e7e
Compare
|
@bors r=petrochenkov rollup |
This comment has been minimized.
This comment has been minimized.
|
❌ Commit 8846e7e has been unapproved due to PR CI failure. Reapprove it with |
8846e7e to
48b2592
Compare
|
@bors r=petrochenkov rollup |
…r=petrochenkov do not complain about unstable target features on nightly This was brought up in rust-lang#162235 (comment): we currently print a warning on nightly saying that using an unstable target feature will become a hard error. That's a mistake. We could either remove the part of the warning that talks about it becoming a hard error, or we could just hide the warning entirely for unstable features on nighty. I went for the latter -- nightly is meant for experimentation with those features so having un-silenceable warnings is not great. Cc @workingjubilee
…uwer Rollup of 15 pull requests Successful merges: - #158936 (Add `std::fs::{Home|Media}Dirs`) - #129036 (Additional NonZero conversions) - #158997 (Avoid recording unnameable `extern crate` aliases in diagnostic metadata) - #161015 (Stabilize `funnel_shifts` (including `const`)) - #161712 (Stabilize `Result::into_{ok,err}`) - #162493 (Add support for -Zsanitizer-cfi-minimal-runtime) - #162655 (next solver: prefer to select impl candidates over global where-clause candidates) - #162862 (Fix intra doc link resolution when a doc comment is composed of both inner and outer doc comment) - #163200 (make `RustaceansAreAwesome` satisfy trait bounds) - #163331 (Move `Arc` and `Rc` into `rcs` mod) - #163427 (implement #![feature(gca_adts)]) - #163428 (do not complain about unstable target features on nightly) - #163444 (Add `stable_rustc` helper in `run-make-support`) - #163447 (Allow using different index types when reading and writing to tables) - #163450 (Force the correct type variable to never for method resolution on an adjusted never type)
…r=petrochenkov do not complain about unstable target features on nightly This was brought up in rust-lang#162235 (comment): we currently print a warning on nightly saying that using an unstable target feature will become a hard error. That's a mistake. We could either remove the part of the warning that talks about it becoming a hard error, or we could just hide the warning entirely for unstable features on nighty. I went for the latter -- nightly is meant for experimentation with those features so having un-silenceable warnings is not great. Cc @workingjubilee
Rollup of 9 pull requests Successful merges: - #161015 (Stabilize `funnel_shifts` (including `const`)) - #161712 (Stabilize `Result::into_{ok,err}`) - #162493 (Add support for -Zsanitizer-cfi-minimal-runtime) - #163427 (implement #![feature(gca_adts)]) - #163390 (add `automatically_derived` attribute documentation) - #163428 (do not complain about unstable target features on nightly) - #163444 (Add `stable_rustc` helper in `run-make-support`) - #163447 (Allow using different index types when reading and writing to tables) - #163459 (Stabilize vec_try_remove)
Rollup of 9 pull requests Successful merges: - rust-lang/rust#161015 (Stabilize `funnel_shifts` (including `const`)) - rust-lang/rust#161712 (Stabilize `Result::into_{ok,err}`) - rust-lang/rust#162493 (Add support for -Zsanitizer-cfi-minimal-runtime) - rust-lang/rust#163427 (implement #![feature(gca_adts)]) - rust-lang/rust#163390 (add `automatically_derived` attribute documentation) - rust-lang/rust#163428 (do not complain about unstable target features on nightly) - rust-lang/rust#163444 (Add `stable_rustc` helper in `run-make-support`) - rust-lang/rust#163447 (Allow using different index types when reading and writing to tables) - rust-lang/rust#163459 (Stabilize vec_try_remove)
Rollup of 9 pull requests Successful merges: - rust-lang/rust#161015 (Stabilize `funnel_shifts` (including `const`)) - rust-lang/rust#161712 (Stabilize `Result::into_{ok,err}`) - rust-lang/rust#162493 (Add support for -Zsanitizer-cfi-minimal-runtime) - rust-lang/rust#163427 (implement #![feature(gca_adts)]) - rust-lang/rust#163390 (add `automatically_derived` attribute documentation) - rust-lang/rust#163428 (do not complain about unstable target features on nightly) - rust-lang/rust#163444 (Add `stable_rustc` helper in `run-make-support`) - rust-lang/rust#163447 (Allow using different index types when reading and writing to tables) - rust-lang/rust#163459 (Stabilize vec_try_remove)
Rollup of 9 pull requests Successful merges: - rust-lang/rust#161015 (Stabilize `funnel_shifts` (including `const`)) - rust-lang/rust#161712 (Stabilize `Result::into_{ok,err}`) - rust-lang/rust#162493 (Add support for -Zsanitizer-cfi-minimal-runtime) - rust-lang/rust#163427 (implement #![feature(gca_adts)]) - rust-lang/rust#163390 (add `automatically_derived` attribute documentation) - rust-lang/rust#163428 (do not complain about unstable target features on nightly) - rust-lang/rust#163444 (Add `stable_rustc` helper in `run-make-support`) - rust-lang/rust#163447 (Allow using different index types when reading and writing to tables) - rust-lang/rust#163459 (Stabilize vec_try_remove)
| // FIXME: Once GCC backend is fixed, remove this `ignore-backends`. | ||
| //@ ignore-backends: gcc | ||
|
|
||
| // Ensure that on stable we don't suggest restricting with an unsafe trait and we continue |
There was a problem hiding this comment.
What does this comment mean? It feels like it's not relevant to the test at all.
(I'm porting this to be an UI test now in #164802)
There was a problem hiding this comment.
Uh, I probably accidentally copied this over from the run-make test I used as template...
I was not able to make this a UI test because it tests stable-only behavior. But maybe there's now a way to do that?
Migrate stable-specific run-make tests to UI tests Enabled by rust-lang#163664. I still kept the `stable_bare_rustc` function, as it could be genuinely useful (just not in the way it was used in run-make tests so far). Should help unblock rust-lang#162848. Note that the comment for the unstable target feature test was wrong (rust-lang#163428 (comment)). r? jieyouxu
Migrate stable-specific run-make tests to UI tests Enabled by rust-lang#163664. I still kept the `stable_bare_rustc` function, as it could be genuinely useful (just not in the way it was used in run-make tests so far). Should help unblock rust-lang#162848. Note that the comment for the unstable target feature test was wrong (rust-lang#163428 (comment)). r? jieyouxu
Migrate stable-specific run-make tests to UI tests Enabled by rust-lang#163664. I still kept the `stable_bare_rustc` function, as it could be genuinely useful (just not in the way it was used in run-make tests so far). Should help unblock rust-lang#162848. Note that the comment for the unstable target feature test was wrong (rust-lang#163428 (comment)). r? jieyouxu
Migrate stable-specific run-make tests to UI tests Enabled by rust-lang#163664. I still kept the `stable_bare_rustc` function, as it could be genuinely useful (just not in the way it was used in run-make tests so far). Should help unblock rust-lang#162848. Note that the comment for the unstable target feature test was wrong (rust-lang#163428 (comment)). r? jieyouxu
This was brought up in #162235 (comment): we currently print a warning on nightly saying that using an unstable target feature will become a hard error. That's a mistake.
We could either remove the part of the warning that talks about it becoming a hard error, or we could just hide the warning entirely for unstable features on nighty. I went for the latter -- nightly is meant for experimentation with those features so having un-silenceable warnings is not great.
Cc @workingjubilee