rust/tests/ui/suggestions/issue-51055-missing-semicolon-between-call-and-tuple.stderr

error[E0618]: expected function, found `bool`
  --> $DIR/issue-51055-missing-semicolon-between-call-and-tuple.rs:4:5
   |
LL |   fn vindictive() -> bool { true }
   |   ----------------------- `vindictive` defined here returns `bool`
...
LL |       vindictive()
   |       -^^^^^^^^^^^- help: consider using a semicolon here to finish the statement: `;`
   |  _____|
   | |
LL | |     (1, 2)
   | |__________- call expression requires function

error: aborting due to previous error

For more information about this error, try `rustc --explain E0618`.
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			error[E0618]: expected function, found `bool`
			`--> $DIR/issue-51055-missing-semicolon-between-call-and-tuple.rs:4:5`
			`\|`
			`LL \| fn vindictive() -> bool { true }`
Use smaller def span for functions Currently, the def span of a funtion encompasses the entire function signature and body. However, this is usually unnecessarily verbose - when we are pointing at an entire function in a diagnostic, we almost always want to point at the signature. The actual contents of the body tends to be irrelevant to the diagnostic we are emitting, and just takes up additional screen space. This commit changes the `def_span` of all function items (freestanding functions, `impl`-block methods, and `trait`-block methods) to be the span of the signature. For example, the function ```rust pub fn foo<T>(val: T) -> T { val } ``` now has a `def_span` corresponding to `pub fn foo<T>(val: T) -> T` (everything before the opening curly brace). Trait methods without a body have a `def_span` which includes the trailing semicolon. For example: ```rust trait Foo { fn bar(); }``` the function definition `Foo::bar` has a `def_span` of `fn bar();` This makes our diagnostic output much shorter, and emphasizes information that is relevant to whatever diagnostic we are reporting. We continue to use the full span (including the body) in a few of places: * MIR building uses the full span when building source scopes. * 'Outlives suggestions' use the full span to sort the diagnostics being emitted. * The `#[rustc_on_unimplemented(enclosing_scope="in this scope")]` attribute points the entire scope body. * The 'unconditional recursion' lint uses the full span to show additional context for the recursive call. All of these cases work only with local items, so we don't need to add anything extra to crate metadata. 2020-08-12 16:02:14 -05:00			\| ----------------------- `vindictive` defined here returns `bool`
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			`...`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| vindictive()`
Detect missing `;` that parses as function call Fix #106515. 2023-08-04 12:22:20 -05:00			\| -^^^^^^^^^^^- help: consider using a semicolon here to finish the statement: `;`
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			`\| _____\|`
			`\| \|`
			`LL \| \| (1, 2)`
			`\| \|__________- call expression requires function`

			`error: aborting due to previous error`

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