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

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

error: aborting due to previous error
Move tests to `ui` 2017-06-23 19:43:35 -05:00			`error[E0308]: mismatched types`
			`--> $DIR/block-must-not-have-result-res.rs:15:9`
			`\|`
Point at return type always when type mismatch against it Before this, the diagnostic errors would only point at the return type when changing it would be a possible solution to a type error. Add a label to the return type without a suggestion to change in order to make the source of the expected type obvious. Follow up to #42850, fixes #25133, fixes #41897. 2017-07-26 00:01:31 -05:00			`14 \| fn drop(&mut self) {`
			\| - expected `()` because of default return type
Move tests to `ui` 2017-06-23 19:43:35 -05:00			`15 \| true //~ ERROR mismatched types`
			`\| ^^^^ expected (), found bool`
			`\|`
			= note: expected type `()`
			found type `bool`

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