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

error[E0618]: expected function, found `i32`
  --> $DIR/issue-10969.rs:2:5
   |
LL | fn func(i: i32) {
   |         - `i32` defined here
LL |     i();
   |     ^--
   |     |
   |     call expression requires function

error[E0618]: expected function, found `i32`
  --> $DIR/issue-10969.rs:6:5
   |
LL |     let i = 0i32;
   |         - `i32` defined here
LL |     i();
   |     ^--
   |     |
   |     call expression requires function

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0618`.
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 22:47:55 +03:00			error[E0618]: expected function, found `i32`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-10969.rs:2:5`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 22:47:55 +03:00			`\|`
Update UI tests 2018-02-23 03:42:32 +03:00			`LL \| fn func(i: i32) {`
Further tweaks to the output - Properly address Variant Ctors - Show signature if span of trait method without `self` is not available 2018-01-15 05:18:06 -08:00			\| - `i32` defined here
Update tests 2019-03-09 15:03:44 +03:00			`LL \| i();`
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 compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 22:47:55 +03:00
			error[E0618]: expected function, found `i32`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-10969.rs:6:5`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 22:47:55 +03:00			`\|`
Update UI tests 2018-02-23 03:42:32 +03:00			`LL \| let i = 0i32;`
Further tweaks to the output - Properly address Variant Ctors - Show signature if span of trait method without `self` is not available 2018-01-15 05:18:06 -08:00			\| - `i32` defined here
Update tests 2019-03-09 15:03:44 +03:00			`LL \| i();`
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 compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 22:47:55 +03:00
			`error: aborting due to 2 previous errors`

update tests 2018-03-03 15:59:40 +01:00			For more information about this error, try `rustc --explain E0618`.