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

enum Whatever {
}

fn foo(x: Whatever) {
    match x {
        Some(field) =>
//~^ ERROR mismatched types
//~| expected `Whatever`, found `Option<_>`
//~| expected enum `Whatever`
//~| found enum `Option<_>`
            field.access(),
    }
}

fn main(){}
rustc: Prevant an out of bounds access in typeck Closes #7092 2014-05-20 22:39:15 -05:00			`enum Whatever {`
			`}`

			`fn foo(x: Whatever) {`
			`match x {`
Update tests with the new error messages 2014-10-20 20:40:15 -05:00			`Some(field) =>`
Fix testsuite errors 2015-01-12 00:01:44 -06:00			`//~^ ERROR mismatched types`
Modify primary span label for E0308 The previous output was unintuitive to users. 2023-01-02 20:00:33 -06:00			//~\| expected `Whatever`, found `Option<_>`
Specific labels when referring to "expected" and "found" types 2019-11-13 16:16:56 -06:00			//~\| expected enum `Whatever`
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 02:40:56 -05:00			//~\| found enum `Option<_>`
Fix whitespace 2016-04-26 11:49:05 -05:00			`field.access(),`
rustc: Prevant an out of bounds access in typeck Closes #7092 2014-05-20 22:39:15 -05:00			`}`
			`}`

			`fn main(){}`