rust/tests/ui/block-result/issue-13624.stderr

error[E0308]: mismatched types
  --> $DIR/issue-13624.rs:7:5
   |
LL |   pub fn get_enum_struct_variant() -> () {
   |                                       -- expected `()` because of return type
LL |     Enum::EnumStructVariant { x: 1, y: 2, z: 3 }
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `()`, found enum `Enum`

error[E0308]: mismatched types
  --> $DIR/issue-13624.rs:20:9
   |
LL |       match enum_struct_variant {
   |             ------------------- this expression has type `()`
LL |         a::Enum::EnumStructVariant { x, y, z } => {
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `()`, found enum `Enum`

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0308`.
Move tests to `ui` 2017-06-23 19:43:35 -05:00			`error[E0308]: mismatched types`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-13624.rs:7:5`
Move tests to `ui` 2017-06-23 19:43:35 -05:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| pub fn get_enum_struct_variant() -> () {`
Readd backticks around () 2017-08-09 11:57:28 -05:00			\| -- expected `()` because of return type
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| Enum::EnumStructVariant { x: 1, y: 2, z: 3 }`
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			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `()`, found enum `Enum`
Move tests to `ui` 2017-06-23 19:43:35 -05:00
			`error[E0308]: mismatched types`
Remove E0308 note when primary label has all info 2019-11-15 01:45:30 -06:00			`--> $DIR/issue-13624.rs:20:9`
Move tests to `ui` 2017-06-23 19:43:35 -05:00			`\|`
Point at the match discriminant when arm pattern has a type mismatch 2019-01-05 19:08:15 -06:00			`LL \| match enum_struct_variant {`
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 00:02:24 -06:00			\| ------------------- this expression has type `()`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| a::Enum::EnumStructVariant { x, y, z } => {`
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			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `()`, found enum `Enum`
Move tests to `ui` 2017-06-23 19:43:35 -05:00
report the total number of errors on compilation failure Prior to this PR, when we aborted because a "critical pass" failed, we displayed the number of errors from that critical pass. While that's the number of errors that caused compilation to abort in that place, that's not what people really want to know. Instead, always report the total number of errors, and don't bother to track the number of errors from the last pass that failed. This changes the compiler driver API to handle errors more smoothly, and therefore is a compiler-api-[breaking-change]. Fixes #42793. 2017-07-02 08:09:09 -05:00			`error: aborting due to 2 previous errors`
Move tests to `ui` 2017-06-23 19:43:35 -05:00
update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0308`.