-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
make coercions to !
in unreachable code a hard error
#45880
Conversation
@bors try |
⌛ Trying commit 2dd1dbfc3041345ba17a9d372412f01eb13a0d32 with merge 371771a40e0262d2b480f622def0e79a1e4b378c... |
☀️ Test successful - status-travis |
Crater started. |
Nice. |
r? @eddyb (just making sure this has an assigned reviewer) |
LGTM, if we actually want to do this, I guess. |
Please rebase onto master and run another try build to pick up fixes in Cargo. |
2dd1dbf
to
491d128
Compare
Force push done. Waiting for another crater run. |
@bors try |
[needs crater] make coercions to `!` in unreachable code a hard error This was added to cover up a lazy extra semicolon in #35849, but does not actually make sense. This is removed as a part of the stabilization of `never_type`.
☀️ Test successful - status-travis |
Crater run started |
Hi @arielb1 (crater requester), @eddyb (reviewer)! Crater results are at: http://cargobomb-reports.s3.amazonaws.com/pr-45580/index.html. 'Blacklisted' crates (spurious failures etc) can be found |
All failures look spurious. |
I suppose we'll merge this with deny-by-default, given that there were no failures on crater |
!
in unreachable code a hard error!
in unreachable code a hard error
src/librustc_lint/lib.rs
Outdated
@@ -247,6 +247,10 @@ pub fn register_builtins(store: &mut lint::LintStore, sess: Option<&Session>) { | |||
id: LintId::of(SAFE_PACKED_BORROWS), | |||
reference: "issue #46043 <https://github.com/rust-lang/rust/issues/46043>", | |||
}, | |||
FutureIncompatibleInfo { | |||
id: LintId::of(COERCE_NEVER), | |||
reference: "issue #46325 <https://github.com/rust-lang/rust/issues/42869>", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link should be fixed (point to an issue related to never type coercion).
15 | #![deny(coerce_never)] | ||
| ^^^^^^^^^^^^ | ||
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! | ||
= note: for more information, see issue #46325 <https://github.com/rust-lang/rust/issues/42869> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And this link.
make coercions to `!` in unreachable code a hard error This was added to cover up a lazy extra semicolon in rust-lang#35849, but does not actually make sense. This is removed as a part of the stabilization of `never_type`.
This was added to cover up a lazy extra semicolon in rust-lang#35849, but does not actually make sense. This is removed as a part of the stabilization of `never_type`.
235de09
to
5a00b7c
Compare
@bors r=nikomatsakis rollup |
📌 Commit 5a00b7c has been approved by |
make coercions to `!` in unreachable code a hard error This was added to cover up a lazy extra semicolon in rust-lang#35849, but does not actually make sense. This is removed as a part of the stabilization of `never_type`.
make coercions to `!` in unreachable code a hard error This was added to cover up a lazy extra semicolon in rust-lang#35849, but does not actually make sense. This is removed as a part of the stabilization of `never_type`.
make coercions to `!` in unreachable code a hard error This was added to cover up a lazy extra semicolon in rust-lang#35849, but does not actually make sense. This is removed as a part of the stabilization of `never_type`.
make coercions to `!` in unreachable code a hard error This was added to cover up a lazy extra semicolon in rust-lang#35849, but does not actually make sense. This is removed as a part of the stabilization of `never_type`.
This was added to cover up a lazy extra semicolon in #35849, but does
not actually make sense. This is removed as a part of the stabilization
of
never_type
.