-
Notifications
You must be signed in to change notification settings - Fork 13.4k
No feature gate error for -> !
used in a trait bound
#120542
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
searched nightlies: from nightly-2023-11-11 to nightly-2024-02-01 bisected with cargo-bisect-rustc v0.6.5Host triple: x86_64-unknown-linux-gnu cargo bisect-rustc --start=1.75.0 --regress success --preserve Then, bisecting
// snip
Regression in https://github.com/rust-lang-ci/rust/commit/4ff2132472c2ba0d56552559c520fe9b4b8384e0
The PR introducing the regression in this rollup is #120316: Don't call `walk_` functions directly if there is an equiva… Manually verified that reverting #120316 (as bdc9ce0) restored the error. cc @GuillaumeGomez |
Not sure to understand why fixing the visitor implementation introduced this bug. Maybe it highlighted a limitation? Gonna check. |
Ok I think I know why: implementation of the |
…gate, r=compiler-errors Correctly check `never_type` feature gating Fixes rust-lang#120542. The feature wasn't tested on return type of a generic function type, so it got under the radar in rust-lang#120316. r? `@compiler-errors`
…gate, r=compiler-errors Correctly check `never_type` feature gating Fixes rust-lang#120542. The feature wasn't tested on return type of a generic function type, so it got under the radar in rust-lang#120316. r? ``@compiler-errors``
WG-prioritization assigning priority (Zulip discussion). @rustbot label -I-prioritize +P-high |
Fix was already approved in #120552. Waiting for CI to be unlocked. |
Rollup merge of rust-lang#120552 - GuillaumeGomez:never-type-feature-gate, r=compiler-errors Correctly check `never_type` feature gating Fixes rust-lang#120542. The feature wasn't tested on return type of a generic function type, so it got under the radar in rust-lang#120316. r? ```@compiler-errors```
Uh oh!
There was an error while loading. Please reload this page.
I tried this code:
I expected to see this happen: “error[E0658]: the
!
type is experimental”Instead, this happened: Successful compilation, as long as I'm using a nightly compiler, but the error when on stable 1.75.
This is incorrect because nightly features should always require
#![feature]
attributes on nightly (until they're stabilized, which hasn't happened yet for!
).Meta
rustc --version --verbose
:@rustbot label +F-never_type +requires-nightly
The text was updated successfully, but these errors were encountered: