rust/tests/ui/parser/issues/issue-58856-2.stderr

error: mismatched closing delimiter: `}`
  --> $DIR/issue-58856-2.rs:6:19
   |
LL | impl Howness for () {
   |                     - closing delimiter possibly meant for this
LL |     fn how_are_you(&self -> Empty {
   |                   ^ unclosed delimiter
...
LL | }
   | ^ mismatched closing delimiter

error: aborting due to 1 previous error
Exit when there are unmatched delims to avoid noisy diagnostics 2023-02-28 07:55:19 +00:00			error: mismatched closing delimiter: `}`
Point at unclosed delimiters as part of the primary MultiSpan Both the place where the parser encounters a needed closed delimiter and the unclosed opening delimiter are important, so they should get the same level of highlighting in the output. 2021-08-27 10:57:28 +00:00			`--> $DIR/issue-58856-2.rs:6:19`
Do not panic on missing close paren Fix #58856. 2019-03-01 16:28:04 -08:00			`\|`
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 08:16:39 +01:00			`LL \| impl Howness for () {`
Exit when there are unmatched delims to avoid noisy diagnostics 2023-02-28 07:55:19 +00:00			`\| - closing delimiter possibly meant for this`
			`LL \| fn how_are_you(&self -> Empty {`
			`\| ^ unclosed delimiter`
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 08:16:39 +01:00			`...`
Do not panic on missing close paren Fix #58856. 2019-03-01 16:28:04 -08:00			`LL \| }`
Exit when there are unmatched delims to avoid noisy diagnostics 2023-02-28 07:55:19 +00:00			`\| ^ mismatched closing delimiter`
Do not panic on missing close paren Fix #58856. 2019-03-01 16:28:04 -08: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`
Do not panic on missing close paren Fix #58856. 2019-03-01 16:28:04 -08:00