rust/tests/ui/error-codes/E0642.stderr

error[E0642]: patterns aren't allowed in methods without bodies
  --> $DIR/E0642.rs:9:12
   |
LL |     fn foo((x, y): (i32, i32));
   |            ^^^^^^
   |
help: give this argument a name or use an underscore to ignore it
   |
LL |     fn foo(_: (i32, i32));
   |            ~

error[E0642]: patterns aren't allowed in methods without bodies
  --> $DIR/E0642.rs:11:12
   |
LL |     fn bar((x, y): (i32, i32)) {}
   |            ^^^^^^
   |
help: give this argument a name or use an underscore to ignore it
   |
LL |     fn bar(_: (i32, i32)) {}
   |            ~

error[E0642]: patterns aren't allowed in methods without bodies
  --> $DIR/E0642.rs:13:15
   |
LL |     fn method(S { .. }: S) {}
   |               ^^^^^^^^
   |
help: give this argument a name or use an underscore to ignore it
   |
LL |     fn method(_: S) {}
   |               ~

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0642`.
Clean up and add extra tests 2018-08-11 15:25:48 -05:00			`error[E0642]: patterns aren't allowed in methods without bodies`
Audit uses of `span_suggestion_short` 2020-07-02 00:32:12 -05:00			`--> $DIR/E0642.rs:9:12`
Emit error for pattern arguments in trait methods The error and check for this already existed, but the parser didn't try to parse trait method arguments as patterns, so the error was never emitted. This surfaces the error, so we get better errors than simple parse errors. 2018-08-03 20:23:21 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| fn foo((x, y): (i32, i32));`
Fix handling of trait methods with bodies and improve efficiency 2018-08-06 12:14:57 -05:00			`\| ^^^^^^`
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages. 2019-10-24 00:20:58 -05:00			`\|`
Emit an error during parsing 2018-08-09 17:23:08 -05:00			`help: give this argument a name or use an underscore to ignore it`
Fix handling of trait methods with bodies and improve efficiency 2018-08-06 12:14:57 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| fn foo(_: (i32, i32));`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`\| ~`
Fix handling of trait methods with bodies and improve efficiency 2018-08-06 12:14:57 -05:00
Clean up and add extra tests 2018-08-11 15:25:48 -05:00			`error[E0642]: patterns aren't allowed in methods without bodies`
Audit uses of `span_suggestion_short` 2020-07-02 00:32:12 -05:00			`--> $DIR/E0642.rs:11:12`
Fix handling of trait methods with bodies and improve efficiency 2018-08-06 12:14:57 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| fn bar((x, y): (i32, i32)) {}`
Fix handling of trait methods with bodies and improve efficiency 2018-08-06 12:14:57 -05:00			`\| ^^^^^^`
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages. 2019-10-24 00:20:58 -05:00			`\|`
Emit an error during parsing 2018-08-09 17:23:08 -05:00			`help: give this argument a name or use an underscore to ignore it`
Fix handling of trait methods with bodies and improve efficiency 2018-08-06 12:14:57 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| fn bar(_: (i32, i32)) {}`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`\| ~`
Emit error for pattern arguments in trait methods The error and check for this already existed, but the parser didn't try to parse trait method arguments as patterns, so the error was never emitted. This surfaces the error, so we get better errors than simple parse errors. 2018-08-03 20:23:21 -05:00
syntax: Fix regression in diagnostics for patterns in trait method parameters 2019-01-01 10:14:00 -06:00			`error[E0642]: patterns aren't allowed in methods without bodies`
Audit uses of `span_suggestion_short` 2020-07-02 00:32:12 -05:00			`--> $DIR/E0642.rs:13:15`
syntax: Fix regression in diagnostics for patterns in trait method parameters 2019-01-01 10:14:00 -06:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| fn method(S { .. }: S) {}`
syntax: Fix regression in diagnostics for patterns in trait method parameters 2019-01-01 10:14:00 -06:00			`\| ^^^^^^^^`
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages. 2019-10-24 00:20:58 -05:00			`\|`
syntax: Fix regression in diagnostics for patterns in trait method parameters 2019-01-01 10:14:00 -06:00			`help: give this argument a name or use an underscore to ignore it`
			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| fn method(_: S) {}`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`\| ~`
syntax: Fix regression in diagnostics for patterns in trait method parameters 2019-01-01 10:14:00 -06:00
			`error: aborting due to 3 previous errors`
Emit error for pattern arguments in trait methods The error and check for this already existed, but the parser didn't try to parse trait method arguments as patterns, so the error was never emitted. This surfaces the error, so we get better errors than simple parse errors. 2018-08-03 20:23:21 -05:00
Add E0642 to parser error 2018-08-09 19:49:45 -05:00			For more information about this error, try `rustc --explain E0642`.