rust/src/test/ui/issues/issue-46771.stderr

error[E0618]: expected function, found `main::Foo`
  --> $DIR/issue-46771.rs:3:23
   |
LL |     struct Foo;
   |     ----------- `main::Foo` defined here
LL |     (1 .. 2).find(|_| Foo(0) == 0); //~ ERROR expected function, found `main::Foo`
   |                       ^^^---
   |                       |
   |                       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 16:11:54 -05:00			error[E0618]: expected function, found `main::Foo`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-46771.rs:3:23`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\|`
			`LL \| struct Foo;`
			\| ----------- `main::Foo` defined here
			LL \| (1 .. 2).find(\|_\| Foo(0) == 0); //~ ERROR expected function, found `main::Foo`
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 22:46:05 -06:00			`\| ^^^---`
			`\| \|`
			`\| call expression requires function`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00
			`error: aborting due to previous error`

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