| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -6304/+0 | |
| 2023-01-02 | Print correct base for too-large literals | clubby789 | -0/+4 | |
| Also update tests | ||||
| 2022-12-13 | Make some diagnostics not depend on the source of what they reference being ↵ | Oli Scherer | -4/+2 | |
| available | ||||
| 2022-11-15 | fix #104088, Slightly improve error message for invalid identifier | yukang | -0/+55 | |
| 2022-10-26 | Rollup 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-22 | Recover unclosed char literal being parsed as lifetime | Michael Goulet | -1/+27 | |
| 2022-10-22 | Stabilize arbitrary_enum_discriminant, take 2 | Deadbeef | -22/+0 | |
| 2022-10-10 | Rollup merge of #102345 - chenyukang:fix-102182-impl-trait, r=estebank | Yuki Okushi | -0/+17 | |
| Recover from impl Trait in type param bound Fixes #102182 r? ``@estebank`` | ||||
| 2022-10-08 | Stabilize half_open_range_patterns | Urgau | -1/+0 | |
| 2022-10-08 | fix #102182, recover from impl Trait in type param bound | yukang | -0/+17 | |
| 2022-09-29 | improve E0585 help | Rageking8 | -2/+2 | |
| 2022-09-27 | fix a ui test | Takayuki Maeda | -0/+2 | |
| 2022-09-27 | add a label to struct/enum/union ident name | Takayuki Maeda | -0/+4 | |
| 2022-09-26 | Rollup merge of #102143 - Rageking8:fix-101540, r=TaKO8Ki | fee1-dead | -0/+17 | |
| Recover from struct nested in struct Fixes #101540 r? `@TaKO8Ki` Not sure If I have done it right. | ||||
| 2022-09-22 | Improve the help message for an invalid calling convention | khyperia | -1/+1 | |
| 2022-09-23 | Fix slight issues with stderr | Rageking8 | -2/+3 | |
| 2022-09-23 | Change UI test stderr | Rageking8 | -4/+3 | |
| 2022-09-22 | recover from struct nested in struct | Rageking8 | -0/+17 | |
| 2022-09-09 | review | lcnr | -10/+10 | |
| 2022-09-08 | merge tests | lcnr | -88/+72 | |
| 2022-09-08 | update ui tests | lcnr | -10/+10 | |
| 2022-08-21 | Rework point-at-arg | Michael Goulet | -2/+2 | |
| 2022-08-05 | Rollup 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-05 | Improve diagnostics for `const a: = expr;` | Maybe Waffle | -2/+2 | |
| 2022-08-05 | Auto merge of #95977 - FabianWolff:issue-92790-dead-tuple, r=estebank | bors | -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-04 | Rollup merge of #98796 - compiler-errors:no-semi-if-comma, r=estebank | Matthias Krüger | -12/+6 | |
| Do not exclusively suggest `;` when `,` is also a choice Fixes #96791 | ||||
| 2022-08-03 | Warn about dead tuple struct fields | Fabian Wolff | -2/+2 | |
| 2022-07-29 | dont call type ascription 'cast' | Michael Goulet | -67/+67 | |
| 2022-07-23 | Do not suggest adding `;` when `,` is also a choice | Michael Goulet | -12/+6 | |
| 2022-07-20 | Suggest returning binding from block or enclosing scope on ↵ | Michael Goulet | -0/+5 | |
| coerce_forced_unit error | ||||
| 2022-07-07 | diagnostics: suggest naming a field after failing to parse | Michael Howell | -5/+14 | |
| 2022-07-07 | diagnostics: mention the `:` token when struct fields fail to parse | Michael Howell | -4/+4 | |
| 2022-06-16 | fix one more case of trailing space | klensy | -10/+10 | |
| 2022-06-16 | diagnostics: fix trailing space | klensy | -29/+29 | |
| 2022-06-13 | Improve parsing errors and suggestions for bad if statements | Michael Goulet | -32/+24 | |
| 2022-06-14 | Rollup merge of #95211 - terrarier2111:improve-parser, r=compiler-errors | Yuki 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-12 | Improves parser diagnostics, fixes #93867 | threadexception | -11/+34 | |
| 2022-06-07 | Auto merge of #97512 - scottmcm:add-coldcc, r=nagisa,lcnr | bors | -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-03 | Fully stabilize NLL | Jack Huey | -3/+2 | |
| 2022-06-02 | add new `emit_inference_failure_err` | lcnr | -1/+6 | |
| 2022-05-30 | Optimize the diagnostic generation for `extern unsafe` | SparrowLii | -6/+1 | |
| 2022-05-30 | Bless tests with the full list of conventions in the output | Scott McMurray | -1/+1 | |
| 2022-05-05 | Allow unused rules in the testsuite where the lint triggers | est31 | -0/+1 | |
| 2022-05-02 | Fix invalid keyword order for function declarations | Ken Matsui | -9/+9 | |
| 2022-04-06 | Stop flagging certain inner attrs as outer ones | León Orell Valerian Liehr | -0/+31 | |
| 2022-03-27 | Provide suggestion for missing `>` in a type parameter list | Esteban 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-22 | diagnostics: 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-18 | suggest removing type ascription in bad position | Michael Goulet | -0/+80 | |
| 2022-03-17 | Rollup merge of #91133 - terrarier2111:unsafe-diagnostic, r=jackh726 | Dylan 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-11 | Format core and std macro rules, removing needless surrounding blocks | David Tolnay | -1/+1 | |
