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

make coercions to ! in unreachable code a hard error #45880

Merged
merged 1 commit into from
Dec 2, 2017

Conversation

arielb1
Copy link
Contributor

@arielb1 arielb1 commented Nov 8, 2017

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.

@arielb1 arielb1 added the S-waiting-on-crater Status: Waiting on a crater run to be completed. label Nov 8, 2017
@arielb1
Copy link
Contributor Author

arielb1 commented Nov 8, 2017

cc @Mark-Simulacrum

@Mark-Simulacrum
Copy link
Member

@bors try

@bors
Copy link
Contributor

bors commented Nov 8, 2017

⌛ Trying commit 2dd1dbfc3041345ba17a9d372412f01eb13a0d32 with merge 371771a40e0262d2b480f622def0e79a1e4b378c...

@bors
Copy link
Contributor

bors commented Nov 9, 2017

☀️ Test successful - status-travis
State: approved= try=True

@Mark-Simulacrum
Copy link
Member

Crater started.

@nikomatsakis
Copy link
Contributor

Nice.

@alexcrichton
Copy link
Member

r? @eddyb

(just making sure this has an assigned reviewer)

@eddyb
Copy link
Member

eddyb commented Nov 12, 2017

LGTM, if we actually want to do this, I guess.

@Mark-Simulacrum
Copy link
Member

Please rebase onto master and run another try build to pick up fixes in Cargo.

@kennytm kennytm added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-crater Status: Waiting on a crater run to be completed. labels Nov 13, 2017
@arielb1
Copy link
Contributor Author

arielb1 commented Nov 15, 2017

@Mark-Simulacrum

Force push done. Waiting for another crater run.

@Mark-Simulacrum
Copy link
Member

@bors try

bors added a commit that referenced this pull request Nov 15, 2017
[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`.
@bors
Copy link
Contributor

bors commented Nov 15, 2017

⌛ Trying commit 491d128 with merge b53e6a8...

@kennytm kennytm added S-waiting-on-crater Status: Waiting on a crater run to be completed. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Nov 15, 2017
@bors
Copy link
Contributor

bors commented Nov 15, 2017

☀️ Test successful - status-travis
State: approved= try=True

@aidanhs
Copy link
Member

aidanhs commented Nov 21, 2017

Crater run started

@aidanhs
Copy link
Member

aidanhs commented Nov 26, 2017

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
here. If you see any spurious failures not on the list, please make a PR against that file.

@arielb1
Copy link
Contributor Author

arielb1 commented Nov 26, 2017

All failures look spurious.

@arielb1
Copy link
Contributor Author

arielb1 commented Nov 26, 2017

I suppose we'll merge this with deny-by-default, given that there were no failures on crater

r? @nikomatsakis

@rust-highfive rust-highfive assigned nikomatsakis and unassigned eddyb Nov 26, 2017
@arielb1 arielb1 changed the title [needs crater] make coercions to ! in unreachable code a hard error make coercions to ! in unreachable code a hard error Nov 26, 2017
@kennytm kennytm added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Nov 26, 2017
@kennytm kennytm removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Nov 29, 2017
@@ -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>",
Copy link

@mzji mzji Nov 30, 2017

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>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And this link.

arielb1 pushed a commit to arielb1/rust that referenced this pull request Nov 30, 2017
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`.
@arielb1
Copy link
Contributor Author

arielb1 commented Nov 30, 2017

@bors r=nikomatsakis rollup

@bors
Copy link
Contributor

bors commented Nov 30, 2017

📌 Commit 5a00b7c has been approved by nikomatsakis

arielb1 pushed a commit to arielb1/rust that referenced this pull request Nov 30, 2017
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`.
arielb1 pushed a commit to arielb1/rust that referenced this pull request Nov 30, 2017
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`.
arielb1 pushed a commit to arielb1/rust that referenced this pull request Nov 30, 2017
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`.
kennytm added a commit to kennytm/rust that referenced this pull request Dec 1, 2017
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`.
bors added a commit that referenced this pull request Dec 1, 2017
Rollup of 13 pull requests

- Successful merges: #45880, #46280, #46373, #46376, #46385, #46386, #46387, #46392, #46400, #46401, #46405, #46412, #46421
- Failed merges:
@bors bors merged commit 5a00b7c into rust-lang:master Dec 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants