rust/tests/ui/macros/empty-trailing-stmt.stderr

error[E0308]: mismatched types
  --> $DIR/empty-trailing-stmt.rs:6:7
   |
LL |     { true }
   |       ^^^^ expected `()`, found `bool`
   |
help: you might have meant to return this value
   |
LL |     { return true; }
   |       ++++++     +

error[E0308]: mismatched types
  --> $DIR/empty-trailing-stmt.rs:5:13
   |
LL | fn foo() -> bool {
   |    ---      ^^^^ expected `bool`, found `()`
   |    |
   |    implicitly returns `()` as its body has no tail or `return` expression

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0308`.
Treat trailing semicolon as a statement in macro call See https://github.com/rust-lang/rust/issues/61733#issuecomment-716188981 We now preserve the trailing semicolon in a macro invocation, even if the macro expands to nothing. As a result, the following code no longer compiles: ```rust macro_rules! empty { () => { } } fn foo() -> bool { //~ ERROR mismatched { true } //~ ERROR mismatched empty!(); } ``` Previously, `{ true }` would be considered the trailing expression, even though there's a semicolon in `empty!();` This makes macro expansion more token-based. 2020-10-25 16:14:19 -05:00			`error[E0308]: mismatched types`
			`--> $DIR/empty-trailing-stmt.rs:6:7`
			`\|`
			`LL \| { true }`
			\| ^^^^ expected `()`, found `bool`
Suggest `return`ing tail expressions that match return type Some newcomers are confused by the behavior of tail expressions, interpreting that "leaving out the `;` makes it the return value". To help them go in the right direction, suggest using `return` instead when applicable. 2021-02-04 14:22:01 -06:00			`\|`
			`help: you might have meant to return this value`
			`\|`
			`LL \| { return true; }`
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 21:07:19 -05:00			`\| ++++++ +`
Treat trailing semicolon as a statement in macro call See https://github.com/rust-lang/rust/issues/61733#issuecomment-716188981 We now preserve the trailing semicolon in a macro invocation, even if the macro expands to nothing. As a result, the following code no longer compiles: ```rust macro_rules! empty { () => { } } fn foo() -> bool { //~ ERROR mismatched { true } //~ ERROR mismatched empty!(); } ``` Previously, `{ true }` would be considered the trailing expression, even though there's a semicolon in `empty!();` This makes macro expansion more token-based. 2020-10-25 16:14:19 -05:00
			`error[E0308]: mismatched types`
			`--> $DIR/empty-trailing-stmt.rs:5:13`
			`\|`
			`LL \| fn foo() -> bool {`
			\| --- ^^^^ expected `bool`, found `()`
			`\| \|`
			\| implicitly returns `()` as its body has no tail or `return` expression

			`error: aborting due to 2 previous errors`

			For more information about this error, try `rustc --explain E0308`.