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

error[E0618]: expected function, found `{float}`
  --> $DIR/issue-45965.rs:2:30
   |
LL |     let a = |r: f64| if r != 0.0(r != 0.0) { 1.0 } else { 0.0 };
   |                              ^^^----------
   |                              |
   |                              call expression requires function

error: aborting due to 1 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 `{float}`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-45965.rs:2:30`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
			`LL \| let a = \|r: f64\| if r != 0.0(r != 0.0) { 1.0 } else { 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
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 14:11:54 -07:00
			For more information about this error, try `rustc --explain E0618`.