rust/tests/ui/block-result/unexpected-return-on-unit.stderr

error[E0308]: mismatched types
  --> $DIR/unexpected-return-on-unit.rs:9:5
   |
LL |     foo()
   |     ^^^^^ expected `()`, found `usize`
   |
help: consider using a semicolon here
   |
LL |     foo();
   |          +
help: try adding a return type
   |
LL | fn bar() -> usize {
   |          ++++++++

error: aborting due to previous error

For more information about this error, try `rustc --explain E0308`.
Move tests to `ui` 2017-06-23 17:43:35 -07:00			`error[E0308]: mismatched types`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/unexpected-return-on-unit.rs:9:5`
Move tests to `ui` 2017-06-23 17:43:35 -07:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| foo()`
Surround types with backticks in type errors 2019-11-15 09:37:01 -08:00			\| ^^^^^ expected `()`, found `usize`
Move tests to `ui` 2017-06-23 17:43:35 -07:00			`\|`
reword `;` suggestions to have consistent wording 2021-02-04 13:59:23 -08:00			`help: consider using a semicolon here`
Only underline suggestion if it is not the only code being shown 2017-07-05 16:39:06 -07:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| foo();`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 19:07:19 -07:00			`\| +`
Adjust new suggestions to the suggestion guidelines 2017-07-21 13:59:17 +02:00			`help: try adding a return type`
Only underline suggestion if it is not the only code being shown 2017-07-05 16:39:06 -07:00			`\|`
Update UI tests 2018-02-25 02:01:39 +03:00			`LL \| fn bar() -> usize {`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 19:07:19 -07:00			`\| ++++++++`
Move tests to `ui` 2017-06-23 17:43:35 -07: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 16:09:09 +03:00			`error: aborting due to previous error`
Move tests to `ui` 2017-06-23 17:43:35 -07:00
update tests 2018-03-03 15:59:40 +01:00			For more information about this error, try `rustc --explain E0308`.