summary refs log tree commit diff
path: root/src/test/ui/parser/issues
AgeCommit message (Collapse)AuthorLines
2022-10-26Rollup merge of #95710 - ↵Dylan DPC-22/+0
fee1-dead-contrib:stabilize_arbitrary_enum_discriminant, r=joshtriplett Stabilize arbitrary_enum_discriminant, take 2 Documentation has been updated in https://github.com/rust-lang/reference/pull/1055. cc #86860 for previous stabilization report. Not yet marks https://github.com/rust-lang/rust/issues/60553 as done: need documentation in the rust reference.
2022-10-22Recover unclosed char literal being parsed as lifetimeMichael Goulet-1/+27
2022-10-22Stabilize arbitrary_enum_discriminant, take 2Deadbeef-22/+0
2022-10-10Rollup merge of #102345 - chenyukang:fix-102182-impl-trait, r=estebankYuki Okushi-0/+17
Recover from impl Trait in type param bound Fixes #102182 r? ``@estebank``
2022-10-08Stabilize half_open_range_patternsUrgau-1/+0
2022-10-08fix #102182, recover from impl Trait in type param boundyukang-0/+17
2022-09-29improve E0585 helpRageking8-2/+2
2022-09-27fix a ui testTakayuki Maeda-0/+2
2022-09-27add a label to struct/enum/union ident nameTakayuki Maeda-0/+4
2022-09-26Rollup merge of #102143 - Rageking8:fix-101540, r=TaKO8Kifee1-dead-0/+17
Recover from struct nested in struct Fixes #101540 r? `@TaKO8Ki` Not sure If I have done it right.
2022-09-22Improve the help message for an invalid calling conventionkhyperia-1/+1
2022-09-23Fix slight issues with stderrRageking8-2/+3
2022-09-23Change UI test stderrRageking8-4/+3
2022-09-22recover from struct nested in structRageking8-0/+17
2022-09-09reviewlcnr-10/+10
2022-09-08merge testslcnr-88/+72
2022-09-08update ui testslcnr-10/+10
2022-08-21Rework point-at-argMichael Goulet-2/+2
2022-08-05Rollup merge of #100168 - ↵Dylan DPC-2/+2
WaffleLapkin:improve_diagnostics_for_missing_type_in_a_const_item, r=compiler-errors Improve diagnostics for `const a: = expr;` Adds a suggestion to write a type when there is a colon, but the type is not present. I've also shrunk spans a little, so the suggestions are a little nicer. Resolves #100146 r? `@compiler-errors`
2022-08-05Improve diagnostics for `const a: = expr;`Maybe Waffle-2/+2
2022-08-05Auto merge of #95977 - FabianWolff:issue-92790-dead-tuple, r=estebankbors-2/+2
Warn about dead tuple struct fields Continuation of #92972. Fixes #92790. The language team has already commented on this in https://github.com/rust-lang/rust/pull/92972#issuecomment-1021511970; I have incorporated their requests here. Specifically, there is now a new allow-by-default `unused_tuple_struct_fields` lint (name bikesheddable), and fields of unit type are ignored (https://github.com/rust-lang/rust/pull/92972#issuecomment-1021815408), so error messages look like this: ``` error: field is never read: `1` --> $DIR/tuple-struct-field.rs:6:21 | LL | struct Wrapper(i32, [u8; LEN], String); | ^^^^^^^^^ | help: change the field to unit type to suppress this warning while preserving the field numbering | LL | struct Wrapper(i32, (), String); | ~~ ``` r? `@joshtriplett`
2022-08-04Rollup merge of #98796 - compiler-errors:no-semi-if-comma, r=estebankMatthias Krüger-12/+6
Do not exclusively suggest `;` when `,` is also a choice Fixes #96791
2022-08-03Warn about dead tuple struct fieldsFabian Wolff-2/+2
2022-07-29dont call type ascription 'cast'Michael Goulet-67/+67
2022-07-23Do not suggest adding `;` when `,` is also a choiceMichael Goulet-12/+6
2022-07-20Suggest returning binding from block or enclosing scope on ↵Michael Goulet-0/+5
coerce_forced_unit error
2022-07-07diagnostics: suggest naming a field after failing to parseMichael Howell-5/+14
2022-07-07diagnostics: mention the `:` token when struct fields fail to parseMichael Howell-4/+4
2022-06-16 fix one more case of trailing spaceklensy-10/+10
2022-06-16diagnostics: fix trailing spaceklensy-29/+29
2022-06-13Improve parsing errors and suggestions for bad if statementsMichael Goulet-32/+24
2022-06-14Rollup merge of #95211 - terrarier2111:improve-parser, r=compiler-errorsYuki Okushi-11/+34
Improve parser diagnostics This pr fixes https://github.com/rust-lang/rust/issues/93867 and contains a couple of diagnostics related changes to the parser. Here is a short list with some of the changes: - don't suggest the same thing that is the current token - suggest removing the current token if the following token is one of the suggestions (maybe incorrect) - tell the user to put a type or lifetime after where if there is none (as a warning) - reduce the amount of tokens suggested (via the new eat_noexpect and check_noexpect methods) If any of these changes are undesirable, i can remove them, thanks!
2022-06-12Improves parser diagnostics, fixes #93867threadexception-11/+34
2022-06-07Auto merge of #97512 - scottmcm:add-coldcc, r=nagisa,lcnrbors-1/+1
Add support for emitting functions with `coldcc` to LLVM The eventual goal is to try using this for things like the internal panicking stuff, to see whether it helps.
2022-06-03Fully stabilize NLLJack Huey-3/+2
2022-06-02add new `emit_inference_failure_err`lcnr-1/+6
2022-05-30Optimize the diagnostic generation for `extern unsafe`SparrowLii-6/+1
2022-05-30Bless tests with the full list of conventions in the outputScott McMurray-1/+1
2022-05-05Allow unused rules in the testsuite where the lint triggersest31-0/+1
2022-05-02Fix invalid keyword order for function declarationsKen Matsui-9/+9
2022-04-06Stop flagging certain inner attrs as outer onesLeón Orell Valerian Liehr-0/+31
2022-03-27Provide suggestion for missing `>` in a type parameter listEsteban Kuber-9/+67
When encountering an inproperly terminated type parameter list, provide a suggestion to close it after the last non-constraint type parameter that was successfully parsed. Fix #94058.
2022-03-22diagnostics: do not suggest `fn foo({ <body> }`Michael Howell-3/+1
Instead of suggesting that the body always replace the last character on the line, presuming it must be a semicolon, the parser should instead check what the last character is, and append the body if it is anything else. Fixes #83104
2022-03-18suggest removing type ascription in bad positionMichael Goulet-0/+80
2022-03-17Rollup merge of #91133 - terrarier2111:unsafe-diagnostic, r=jackh726Dylan DPC-1/+6
Improve `unsafe` diagnostic This fixes: https://github.com/rust-lang/rust/issues/90880 I didn't use the exact proposed messages though.
2022-03-11Format core and std macro rules, removing needless surrounding blocksDavid Tolnay-1/+1
2022-03-05Do not point at whole file missing `fn main`Esteban Kuber-2/+2
Only point at the end of the crate. We could try making it point at the beginning of the crate, but that is confused with `DUMMY_SP`, causing the output to be *worse*. This change will make it so that VSCode will *not* underline the whole file when `main` is missing, so other errors will be visible.
2022-02-28Tweak diagnosticsEsteban Kuber-4/+3
* Recover from invalid `'label: ` before block. * Make suggestion to enclose statements in a block multipart. * Point at `match`, `while`, `loop` and `unsafe` keywords when failing to parse their expression. * Do not suggest `{ ; }`. * Do not suggest `|` when very unlikely to be what was wanted (in `let` statements).
2022-02-12Rollup merge of #93595 - compiler-errors:ice-on-lifetime-arg, r=jackh726Matthias Krüger-1/+24
fix ICE when parsing lifetime as function argument I don't really like this, but we basically need to emit an error instead of just delaying an bug, because there are too many places in the AST that aren't covered by my previous PRs... cc: https://github.com/rust-lang/rust/issues/93282#issuecomment-1028052945
2022-02-02Add more *-unwind ABI variantsAmanieu d'Antras-1/+1
The following *-unwind ABIs are now supported: - "C-unwind" - "cdecl-unwind" - "stdcall-unwind" - "fastcall-unwind" - "vectorcall-unwind" - "thiscall-unwind" - "aapcs-unwind" - "win64-unwind" - "sysv64-unwind" - "system-unwind"
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-27 19:41:03 +0000