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

error[E0308]: mismatched types
  --> $DIR/issue-50585.rs:2:18
   |
LL |     |y: Vec<[(); for x in 0..2 {}]>| {};
   |                  ^^^^^^^^^^^^^^^^ expected `usize`, found `()`
   |
   = note: `for` loops evaluate to unit type `()`
help: consider returning a value here
   |
LL |     |y: Vec<[(); for x in 0..2 {} /* `usize` value */]>| {};
   |                                   +++++++++++++++++++

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0308`.
Accept `TyError` in patterns to avoid ICE on bad input 2018-06-21 18:18:39 -07:00			`error[E0308]: mismatched types`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-50585.rs:2:18`
Accept `TyError` in patterns to avoid ICE on bad input 2018-06-21 18:18:39 -07:00			`\|`
			`LL \| \|y: Vec<[(); for x in 0..2 {}]>\| {};`
Surround types with backticks in type errors 2019-11-15 09:37:01 -08:00			\| ^^^^^^^^^^^^^^^^ expected `usize`, found `()`
Remove note about iteration count in coerce and replace it with a simple note suggesting returning a value. The type mismatch error was never due to how many times the loop iterates. It is more because of the peculiar structure of what the for loop desugars to. So the note talking about iteration count didn't make sense 2024-04-19 18:30:28 +05:30			`\|`
			= note: `for` loops evaluate to unit type `()`
			`help: consider returning a value here`
			`\|`
			LL \| \|y: Vec<[(); for x in 0..2 {} /* `usize` value */]>\| {};
			`\| +++++++++++++++++++`
Accept `TyError` in patterns to avoid ICE on bad input 2018-06-21 18:18:39 -07:00
Get rid of HIR const checker 2024-11-22 02:31:42 +00:00			`error: aborting due to 1 previous error`
Accept `TyError` in patterns to avoid ICE on bad input 2018-06-21 18:18:39 -07:00
Get rid of HIR const checker 2024-11-22 02:31:42 +00:00			For more information about this error, try `rustc --explain E0308`.