You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
expected: type error on line r { }, because type of 0 is not tuple but r is.
result: compile error
log:
rust: task failed at 'Unsupported constant expr', <core-macros>:15
error: internal compiler error: unexpected failure
note: the compiler hit an unexpected failure path.this is a bug
note: try running with RUST_LOG=rustc=1,::rt::backtrace to get further details and report the results to github.com/mozilla/rust/issues
rust: task failed at 'explicit failure', <core-macros>:15
rust: domain main @0x7fd30b80c810 root task failed
Case 2: Unexpected silence and strange behavior
Input:
Don't understand the first one, but I've run in the second case myself, see #4612.
The error messages are completely correct, just misleading.
fn main() {
let a_tuple = (1, 2); // Introduces new local variable 'a_tuple'
match 0 {
a_tuple => { // Matches every possible value and binds them to a new local variable 'a_tuple'
io::println("A"); // That variable never gets used here, hence the warning
}
_ => { // Because the above arm matches everything, this arm can never be reached
io::println("B");
}
}
}
Fix ICE on `unsound_collection_transmute`
Fixesrust-lang#4968
Check if `Ty`s are normalizable. It might show hidden false negative, I'm not sure.
Also, the regression tests are placed on two dirs, so move them to `/crashes`. I think it will be easier to find the right place.
changelog: Fix ICE on `unsound_collection_transmute`
Case 1: Unexpected path error
Input code
expected: type error on line r { }, because type of 0 is not tuple but r is.
result: compile error
log:
Case 2: Unexpected silence and strange behavior
Input:
Expected: type error on line r { }, because type of 0 is not tuple but r is.
Result: Unexpected warnings, silence complie and unexpected behavior.
Warnings:
It should not be 'unused variable'
Output with execution:
0 looks matched to (1,2)
Even more, trying next:
Unreachable _ error is raised.
The text was updated successfully, but these errors were encountered: