-
Notifications
You must be signed in to change notification settings - Fork 360
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
Bump rustc version to fix miri #1138
Bump rustc version to fix miri #1138
Conversation
@bors r+ |
📌 Commit 959033c has been approved by |
…king, r=oli-obk Bump rustc version to fix miri Fixes rust-lang/rust#67793
☀️ Test successful - checks-travis, status-appveyor |
@@ -1,3 +1,5 @@ | |||
#![allow(const_err)] // don't warn about truncating casts |
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.
Wait, so hard errors inside constants and const-prop-originating warnings outside constants use the same lint name? Isn't that odd?
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.
Ah no, turns out rust-lang/rust#67676 made these overflows err-by-default, actually. Interesting.
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.
But to me the lint looks wrong here:
enum Signed {
Bar = -42,
Baz,
Quux = 100,
}
fn signed() -> [i8; 3] {
let baz = Signed::Baz; // let-expansion changes the MIR significantly
[Signed::Bar as i8, baz as i8, Signed::Quux as i8]
}
Signed::Bar
is -42 which is well inside the range of i8
. So why is there an error shown?
Fixes rust-lang/rust#67793