rust/tests/ui/tail-typeck.stderr

error[E0308]: mismatched types
  --> $DIR/tail-typeck.rs:3:26
   |
LL | fn f() -> isize { return g(); }
   |           -----          ^^^ expected `isize`, found `usize`
   |           |
   |           expected `isize` because of return type
   |
help: you can convert a `usize` to an `isize` and panic if the converted value doesn't fit
   |
LL | fn f() -> isize { return g().try_into().unwrap(); }
   |                             ++++++++++++++++++++

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0308`.
Moved compile-fail tests to ui tests. 2018-08-08 20:28:26 +08:00			`error[E0308]: mismatched types`
Remove licenses 2018-12-25 23:56:47 +08:00			`--> $DIR/tail-typeck.rs:3:26`
Moved compile-fail tests to ui tests. 2018-08-08 20:28:26 +08:00			`\|`
			`LL \| fn f() -> isize { return g(); }`
Surround types with backticks in type errors 2019-11-16 01:37:01 +08:00			\| ----- ^^^ expected `isize`, found `usize`
Point at return type when appropriate 2019-01-18 16:12:09 +08:00			`\| \|`
			\| expected `isize` because of return type
Emit coercion suggestions in more places Fixes #66910 We have several different kinds of suggestions we can try to make when type coercion fails. However, we were previously only emitting these suggestions from `demand_coerce_diag`. This resulted in the compiler failing to emit applicable suggestions in several different cases, such as when the implicit return value of a function had the wrong type. This commit adds a new `emit_coerce_suggestions` method, which tries to emit a number of related suggestions. This method is called from both `demand_coerce_diag` and `CoerceMany::coerce_inner`, which covers a much wider range of cases than before. We now suggest using `.await` in more cases where it is applicable, among other improvements. 2019-12-04 09:32:50 +08:00			`\|`
Say "doesn't" instead of "wouldn't" in convert message 2020-09-30 10:27:58 +08:00			help: you can convert a `usize` to an `isize` and panic if the converted value doesn't fit
Emit coercion suggestions in more places Fixes #66910 We have several different kinds of suggestions we can try to make when type coercion fails. However, we were previously only emitting these suggestions from `demand_coerce_diag`. This resulted in the compiler failing to emit applicable suggestions in several different cases, such as when the implicit return value of a function had the wrong type. This commit adds a new `emit_coerce_suggestions` method, which tries to emit a number of related suggestions. This method is called from both `demand_coerce_diag` and `CoerceMany::coerce_inner`, which covers a much wider range of cases than before. We now suggest using `.await` in more cases where it is applicable, among other improvements. 2019-12-04 09:32:50 +08:00			`\|`
			`LL \| fn f() -> isize { return g().try_into().unwrap(); }`
Use smaller spans for some structured suggestions Use more accurate suggestion spans for * argument parse error * fully qualified path * missing code block type * numeric casts * E0212 2021-08-10 18:53:43 +08:00			`\| ++++++++++++++++++++`
Moved compile-fail tests to ui tests. 2018-08-08 20:28:26 +08:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 23:44:16 +08:00			`error: aborting due to 1 previous error`
Moved compile-fail tests to ui tests. 2018-08-08 20:28:26 +08:00
			For more information about this error, try `rustc --explain E0308`.