rust/src/test/ui/issues/issue-34334.rs

fn main () {
    let sr: Vec<(u32, _, _) = vec![];
    //~^ ERROR only path types can be used in associated type constraints
    let sr2: Vec<(u32, _, _)> = sr.iter().map(|(faction, th_sender, th_receiver)| {}).collect();
    //~^ ERROR a value of type `Vec<(u32, _, _)>` cannot be built
}
Fix ICE in memory categorization of tuple patterns 2016-06-18 02:49:44 +03:00			`fn main () {`
Recover from parse error in tuple syntax 2019-03-26 17:36:07 -07:00			`let sr: Vec<(u32, _, _) = vec![];`
add tests 2020-11-21 15:44:06 +01:00			`//~^ ERROR only path types can be used in associated type constraints`
Fix ICE in memory categorization of tuple patterns 2016-06-18 02:49:44 +03:00			`let sr2: Vec<(u32, _, _)> = sr.iter().map(\|(faction, th_sender, th_receiver)\| {}).collect();`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 10:40:56 +03:00			//~^ ERROR a value of type `Vec<(u32, _, _)>` cannot be built
Fix ICE in memory categorization of tuple patterns 2016-06-18 02:49:44 +03:00			`}`