rust/tests/ui/parser/unclosed_delim_mod.stderr

error: mismatched closing delimiter: `}`
  --> $DIR/unclosed_delim_mod.rs:5:7
   |
LL | pub fn new() -> Result<Value, ()> {
   |                                   - closing delimiter possibly meant for this
LL |     Ok(Value {
   |       ^ unclosed delimiter
LL |     }
LL | }
   | ^ mismatched closing delimiter

error: aborting due to previous error
tweak wording of mismatched delimiter errors 2020-01-03 13:40:15 +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/unclosed_delim_mod.rs:5:7`
Add regression test for #58886 2019-03-04 00:59:24 +00:00			`\|`
			`LL \| pub fn new() -> Result<Value, ()> {`
tweak wording of mismatched delimiter errors 2020-01-03 13:40:15 +00:00			`\| - closing delimiter possibly meant for this`
Add regression test for #58886 2019-03-04 00:59:24 +00:00			`LL \| Ok(Value {`
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			`\| ^ unclosed delimiter`
Add regression test for #58886 2019-03-04 00:59:24 +00:00			`LL \| }`
			`LL \| }`
tweak wording of mismatched delimiter errors 2020-01-03 13:40:15 +00:00			`\| ^ mismatched closing delimiter`
Add regression test for #58886 2019-03-04 00:59:24 +00:00
Provide a span if main function is not present in crate Unfortunately, the diagnotic machinery does not cope well with an empty span which can happen if the crate is empty, in which case we merely set a spanless note. 2019-09-08 17:06:49 +00:00			`error: aborting due to previous error`
Add regression test for #58886 2019-03-04 00:59:24 +00:00