rust/tests/ui/parser/removed-syntax-with-2.stderr

error: expected one of `,`, `:`, or `}`, found `a`
  --> $DIR/removed-syntax-with-2.rs:8:31
   |
LL |     let b = S { foo: (), with a };
   |             -            ---- ^ expected one of `,`, `:`, or `}`
   |             |            |
   |             |            while parsing this struct field
   |             while parsing this struct

error[E0063]: missing field `bar` in initializer of `S`
  --> $DIR/removed-syntax-with-2.rs:8:13
   |
LL |     let b = S { foo: (), with a };
   |             ^ missing `bar`

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0063`.
diagnostics: mention the `:` token when struct fields fail to parse 2022-07-07 16:59:54 -05:00			error: expected one of `,`, `:`, or `}`, found `a`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00			`--> $DIR/removed-syntax-with-2.rs:8:31`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00			`\|`
			`LL \| let b = S { foo: (), with a };`
Detect missing `=>` after match guard during parsing ``` error: expected one of `,`, `:`, or `}`, found `.` --> $DIR/missing-fat-arrow.rs:25:14 \| LL \| Some(a) if a.value == b { \| - while parsing this struct LL \| a.value = 1; \| -^ expected one of `,`, `:`, or `}` \| \| \| while parsing this struct field \| help: try naming a field \| LL \| a: a.value = 1; \| ++ help: you might have meant to start a match arm after the match guard \| LL \| Some(a) if a.value == b => { \| ++ ``` Fix #78585. 2023-10-03 16:21:02 -05:00			\| - ---- ^ expected one of `,`, `:`, or `}`
			`\| \| \|`
			`\| \| while parsing this struct field`
Recover from parse errors in struct literal fields Attempt to recover from parse errors while parsing a struct's literal fields by skipping tokens until a comma or the closing brace is found. This allows errors in other fields to be reported. 2019-01-20 02:37:06 -06:00			`\| while parsing this struct`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 02:40:56 -05:00			error[E0063]: missing field `bar` in initializer of `S`
Tweak field parse error recovery 2019-01-20 17:16:36 -06:00			`--> $DIR/removed-syntax-with-2.rs:8:13`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00			`\|`
			`LL \| let b = S { foo: (), with a };`
Tweak field parse error recovery 2019-01-20 17:16:36 -06:00			\| ^ missing `bar`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00
Tweak field parse error recovery 2019-01-20 17:16:36 -06:00			`error: aborting due to 2 previous errors`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00
Tweak field parse error recovery 2019-01-20 17:16:36 -06:00			For more information about this error, try `rustc --explain E0063`.