rust/tests/ui/issues/issue-20714.stderr

error[E0618]: expected function, found struct `G`
  --> $DIR/issue-20714.rs:4:13
   |
LL | struct G;
   | -------- struct `G` defined here
...
LL |     let g = G();
   |             ^--
   |             |
   |             call expression requires function
   |
help: `G` is a unit struct, and does not take parentheses to be constructed
   |
LL -     let g = G();
LL +     let g = G;
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0618`.
Be more precise when suggesting removal of parens on unit adt ctor 2022-07-16 22:15:41 +00:00			error[E0618]: expected function, found struct `G`
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/issue-20714.rs:4:13`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
			`LL \| struct G;`
Be more precise when suggesting removal of parens on unit adt ctor 2022-07-16 22:15:41 +00:00			\| -------- struct `G` defined here
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`...`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| let g = G();`
in which the E0618 "expected function" diagnostic gets a makeover Now the main span focuses on the erroneous not-a-function callee, while showing the entire call expression is relegated to a secondary span. In the case where the erroneous callee is itself a call, we point out the definition, and, if the call expression spans multiple lines, tentatively suggest a semicolon (because we suspect that the "outer" call is actually supposed to be a tuple). The new `bug!` assertion is, in fact, safe (`confirm_builtin_call` is only called by `check_call`, which is only called with a first arg of kind `ExprKind::Call` in `check_expr_kind`). Resolves #51055. 2018-11-11 04:46:05 +00:00			`\| ^--`
			`\| \|`
			`\| call expression requires function`
Be more precise when suggesting removal of parens on unit adt ctor 2022-07-16 22:15:41 +00:00			`\|`
			help: `G` is a unit struct, and does not take parentheses to be constructed
			`\|`
			`LL - let g = G();`
			`LL + let g = G;`
			`\|`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
			For more information about this error, try `rustc --explain E0618`.