-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Fix never-type rvalue ICE #47746
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
Merged
Merged
Fix never-type rvalue ICE #47746
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
// Copyright 2017 The Rust Project Developers. See the COPYRIGHT | ||
// file at the top-level directory of this distribution and at | ||
// http://rust-lang.org/COPYRIGHT. | ||
// | ||
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or | ||
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license | ||
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your | ||
// option. This file may not be copied, modified, or distributed | ||
// except according to those terms. | ||
|
||
#![feature(never_type)] | ||
#![allow(dead_code)] | ||
#![allow(path_statements)] | ||
#![allow(unreachable_patterns)] | ||
|
||
fn never_direct(x: !) { | ||
x; | ||
} | ||
|
||
fn never_ref_pat(ref x: !) { | ||
*x; | ||
} | ||
|
||
fn never_ref(x: &!) { | ||
let &y = x; | ||
y; | ||
} | ||
|
||
fn never_pointer(x: *const !) { | ||
unsafe { | ||
*x; | ||
} | ||
} | ||
|
||
fn never_slice(x: &[!]) { | ||
x[0]; | ||
} | ||
|
||
fn never_match(x: Result<(), !>) { | ||
match x { | ||
Ok(_) => {}, | ||
Err(_) => {}, | ||
} | ||
} | ||
|
||
pub fn main() { } |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Just to be sure I understand, the premise here is that the type is either
()
or else the block must diverge, since any other type would have yielded a compilation error?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.
Yeah, with the current semantics, any other type should be impossible (i.e. any other type must be explicit and go through the
Some(expr)
branch instead) , because the only implicit return types are()
and!
.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.
Could we have a comment? That's a bit non-obvious. (If the code were like
if ty.is_never()
it'd be more obvious...)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.
Sure. (The reason I opted for
ty.is_nil()
rather thanty.is_never()
here is because it seemed less contextual — it's always true that we only want to assign a unit if the type is unit. One alternative to make it absolutely explicit would be to check for!ty.is_never()
in anelse
clause and throw a warning there that it should be impossible, but this seems like overkill.)