rust/tests/ui/block-result/block-must-not-have-result-res.stderr

error[E0308]: mismatched types
  --> $DIR/block-must-not-have-result-res.rs:5:9
   |
LL |     fn drop(&mut self) {
   |                       - expected `()` because of default return type
LL |         true
   |         ^^^^ expected `()`, found `bool`

error: aborting due to previous error

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/block-must-not-have-result-res.rs:5:9`
Move tests to `ui` 2017-06-23 19:43:35 -05:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| fn drop(&mut self) {`
Point to where missing return type should go 2023-09-30 14:29:41 -05:00			\| - expected `()` because of default return type
Update tests 2019-03-09 06:03:44 -06:00			`LL \| true`
Surround types with backticks in type errors 2019-11-15 11:37:01 -06:00			\| ^^^^ expected `()`, found `bool`
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 previous error`
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`.