granite-rust/tests/ui/issues/issue-46771.stderr

error[E0618]: expected function, found `Foo`
  --> $DIR/issue-46771.rs:3:23
   |
LL |     struct Foo;
   |     ---------- `Foo` defined here
LL |     (1 .. 2).find(|_| Foo(0) == 0);
   |                       ^^^---
   |                       |
   |                       call expression requires function

error: aborting due to previous error

For more information about this error, try `rustc --explain E0618`.
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 10:40:56 +03:00			error[E0618]: expected function, found `Foo`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-46771.rs:3:23`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
			`LL \| struct Foo;`
Shorten def_span for more items. 2022-02-13 16:27:59 +01:00			\| ---------- `Foo` defined here
Update tests 2019-03-09 15:03:44 +03:00			`LL \| (1 .. 2).find(\|_\| Foo(0) == 0);`
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`.