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
fn main () {
let sr: Vec<(u32, _, _) = vec![];
let sr2: Vec<(u32, _, _)> = sr.iter().map(|(faction, th_sender, th_receiver)| {}).collect();
}
I expected to see this happen:
error: missing >
Instead, this happened:
> t.rs:2:29: 2:30 error: expected one of `+`, `,`, or `>`, found `=`
> t.rs:2 let sr: Vec<(u32, _, _) = vec![];
> ^
> t.rs:3:33: 3:35 error: unresolved name `sr` [E0425]
> t.rs:3 let sr2: Vec<(u32, _, _)> = sr.iter().map(|(faction, th_sender, th_receiver)| {}).collect();
> ^~
> t.rs:3:33: 3:35 help: run `rustc --explain E0425` to see a detailed explanation
> t.rs:3:48: 3:81 error: internal compiler error: src/librustc/middle/mem_categorization.rs:1300: tuple pattern unexpected type Err(())
> t.rs:3 let sr2: Vec<(u32, _, _)> = sr.iter().map(|(faction, th_sender, th_receiver)| {}).collect();
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> note: the compiler unexpectedly panicked. this is a bug.
> note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
> thread 'rustc' panicked at 'Box<Any>', src/libsyntax/errors/mod.rs:545
> note: Run with `RUST_BACKTRACE=1` for a backtrace.
Fix ICE in memory categorization of tuple patterns
Fixes#34334
It seems to be ok for `pat_ty` to return `Err` even if type checking is done, because it uses `infcx.node_ty` which is supposed to return `Err` for all kinds of erroneous types so its callers could quickly bail out with `?`.
r? @arielb1
I tried this code:
I expected to see this happen:
Instead, this happened:
Meta
rustc --version --verbose
:rustc 1.11.0-dev
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.11.0-dev
Backtrace:
The text was updated successfully, but these errors were encountered: