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

error[E0618]: expected function, found `&str`
  --> $DIR/issue-22468.rs:3:13
   |
LL |     let foo = "bar";
   |         --- `foo` has type `&str`
LL |     let x = foo("baz");
   |             ^^^-------
   |             |
   |             call expression requires function

error: aborting due to previous error

For more information about this error, try `rustc --explain E0618`.
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			error[E0618]: expected function, found `&str`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-22468.rs:3:13`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
			`LL \| let foo = "bar";`
add helpful error notes and fix the false 'defined here' messages 2021-02-17 20:20:59 +05:30			\| --- `foo` has type `&str`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`LL \| let x = foo("baz");`
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-10 20:46:05 -08:00			`\| ^^^-------`
			`\| \|`
			`\| call expression requires function`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
			`error: aborting due to previous error`

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