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

error[E0308]: mismatched types
  --> $DIR/issue-7092.rs:6:9
   |
LL |     match x {
   |           - this expression has type `Whatever`
LL |         Some(field) =>
   |         ^^^^^^^^^^^ expected `Whatever`, found `Option<_>`
   |
   = note: expected enum `Whatever`
              found enum `Option<_>`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0308`.
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`error[E0308]: mismatched types`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-7092.rs:6:9`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
Point at the match discriminant when arm pattern has a type mismatch 2019-01-05 17:08:15 -08:00			`LL \| match x {`
MatchExpressionArmPattern: Use more generic wording. The existing wording was inappropriate for e.g. `if let Ok(_) = expr { .. }`. The diagnostic would leak the fact that we desugar to a `match`. 2019-12-30 07:02:24 +01:00			\| - this expression has type `Whatever`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`LL \| Some(field) =>`
Modify primary span label for E0308 The previous output was unintuitive to users. 2023-01-02 18:00:33 -08:00			\| ^^^^^^^^^^^ expected `Whatever`, found `Option<_>`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
Specific labels when referring to "expected" and "found" types 2019-11-13 14:16:56 -08:00			= note: 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 10:40:56 +03:00			found enum `Option<_>`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0308`.