rust/tests/ui/issues/issue-7061.rs

struct BarStruct;

impl<'a> BarStruct {
    fn foo(&'a mut self) -> Box<BarStruct> { self }
    //~^ ERROR mismatched types
    //~| expected struct `Box<BarStruct>`
    //~| found mutable reference `&'a mut BarStruct`
}

fn main() {}
test: Add some tests for closed issues Closes #6738 Closes #7061 Closes #7899 Closes #9719 Closes #10028 Closes #10228 Closes #10401 Closes #11192 Closes #11508 Closes #11529 Closes #11873 Closes #11925 2014-03-06 09:55:35 -08:00			`struct BarStruct;`

			`impl<'a> BarStruct {`
tests: remove uses of Gc. 2014-10-02 08:10:09 +03:00			`fn foo(&'a mut self) -> Box<BarStruct> { self }`
Fix testsuite errors 2015-01-12 01:01:44 -05:00			`//~^ ERROR mismatched types`
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			//~\| expected struct `Box<BarStruct>`
Specific labels when referring to "expected" and "found" types 2019-11-13 14:16:56 -08:00			//~\| found mutable reference `&'a mut BarStruct`
test: Add some tests for closed issues Closes #6738 Closes #7061 Closes #7899 Closes #9719 Closes #10028 Closes #10228 Closes #10401 Closes #11192 Closes #11508 Closes #11529 Closes #11873 Closes #11925 2014-03-06 09:55:35 -08:00			`}`

			`fn main() {}`