rust/src/test/ui/issues/issue-24036.stderr

error[E0308]: mismatched types
  --> $DIR/issue-24036.rs:3:9
   |
LL |     let mut x = |c| c + 1;
   |                 --------- the expected closure
LL |     x = |c| c + 1;
   |         ^^^^^^^^^ expected closure, found a different closure
   |
   = note: expected closure `[closure@$DIR/issue-24036.rs:2:17: 2:26]`
              found closure `[closure@$DIR/issue-24036.rs:3:9: 3:18]`
   = note: no two closures, even if identical, have the same type
   = help: consider boxing your closure and/or using it as a trait object

error[E0308]: `match` arms have incompatible types
  --> $DIR/issue-24036.rs:10:14
   |
LL |       let x = match 1usize {
   |  _____________-
LL | |         1 => |c| c + 1,
   | |              --------- this is found to be of type `[closure@$DIR/issue-24036.rs:9:14: 9:23]`
LL | |         2 => |c| c - 1,
   | |              ^^^^^^^^^ expected closure, found a different closure
LL | |         _ => |c| c - 1
LL | |     };
   | |_____- `match` arms have incompatible types
   |
   = note: expected type `[closure@$DIR/issue-24036.rs:9:14: 9:23]`
           found closure `[closure@$DIR/issue-24036.rs:10:14: 10:23]`
   = note: no two closures, even if identical, have the same type
   = help: consider boxing your closure and/or using it as a trait object

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0308`.
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00			`error[E0308]: mismatched types`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-24036.rs:3:9`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00			`\|`
Point at opaque and closure type definitions in type errors 2019-11-15 20:53:17 -06:00			`LL \| let mut x = \|c\| c + 1;`
review comments 2019-12-15 16:05:08 -06:00			`\| --------- the expected closure`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| x = \|c\| c + 1;`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00			`\| ^^^^^^^^^ expected closure, found a different closure`
			`\|`
Specific labels when referring to "expected" and "found" types 2019-11-13 16:16:56 -06:00			= note: expected closure `[closure@$DIR/issue-24036.rs:2:17: 2:26]`
			found closure `[closure@$DIR/issue-24036.rs:3:9: 3:18]`
Closure type error ui tweak Do not point at the same span on all notes/help messages, and instead show them without a span. 2017-12-19 21:04:09 -06:00			`= note: no two closures, even if identical, have the same type`
			`= help: consider boxing your closure and/or using it as a trait object`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00
Add backticks to various diagnostics 2020-01-04 18:17:46 -06:00			error[E0308]: `match` arms have incompatible types
Reweork incompatible match arms error - Point at the body expression of the match arm with the type error. - Point at the prior match arms explicitely stating the evaluated type. - Point at the entire match expr in a secondary span, instead of primary. - For type errors in the first match arm, the cause is outside of the match, treat as implicit block error to give a more appropriate error. 2019-02-07 07:39:54 -06:00			`--> $DIR/issue-24036.rs:10:14`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| let x = match 1usize {`
Reweork incompatible match arms error - Point at the body expression of the match arm with the type error. - Point at the prior match arms explicitely stating the evaluated type. - Point at the entire match expr in a secondary span, instead of primary. - For type errors in the first match arm, the cause is outside of the match, treat as implicit block error to give a more appropriate error. 2019-02-07 07:39:54 -06:00			`\| _____________-`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| \| 1 => \|c\| c + 1,`
Reweork incompatible match arms error - Point at the body expression of the match arm with the type error. - Point at the prior match arms explicitely stating the evaluated type. - Point at the entire match expr in a secondary span, instead of primary. - For type errors in the first match arm, the cause is outside of the match, treat as implicit block error to give a more appropriate error. 2019-02-07 07:39:54 -06:00			\| \| --------- this is found to be of type `[closure@$DIR/issue-24036.rs:9:14: 9:23]`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| \| 2 => \|c\| c - 1,`
Reweork incompatible match arms error - Point at the body expression of the match arm with the type error. - Point at the prior match arms explicitely stating the evaluated type. - Point at the entire match expr in a secondary span, instead of primary. - For type errors in the first match arm, the cause is outside of the match, treat as implicit block error to give a more appropriate error. 2019-02-07 07:39:54 -06:00			`\| \| ^^^^^^^^^ expected closure, found a different closure`
Update UI tests 2018-02-24 17:01:39 -06:00			`LL \| \| _ => \|c\| c - 1`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| \| };`
Reweork incompatible match arms error - Point at the body expression of the match arm with the type error. - Point at the prior match arms explicitely stating the evaluated type. - Point at the entire match expr in a secondary span, instead of primary. - For type errors in the first match arm, the cause is outside of the match, treat as implicit block error to give a more appropriate error. 2019-02-07 07:39:54 -06:00			\| \|_____- `match` arms have incompatible types
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00			`\|`
Reweork incompatible match arms error - Point at the body expression of the match arm with the type error. - Point at the prior match arms explicitely stating the evaluated type. - Point at the entire match expr in a secondary span, instead of primary. - For type errors in the first match arm, the cause is outside of the match, treat as implicit block error to give a more appropriate error. 2019-02-07 07:39:54 -06:00			= note: expected type `[closure@$DIR/issue-24036.rs:9:14: 9:23]`
Specific labels when referring to "expected" and "found" types 2019-11-13 16:16:56 -06:00			found closure `[closure@$DIR/issue-24036.rs:10:14: 10:23]`
Closure type error ui tweak Do not point at the same span on all notes/help messages, and instead show them without a span. 2017-12-19 21:04:09 -06:00			`= note: no two closures, even if identical, have the same type`
			`= help: consider boxing your closure and/or using it as a trait object`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00
			`error: aborting due to 2 previous errors`

update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0308`.