| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2020-02-24 | parse: tweak diagnostic wordings | Mazdak Farrokhzad | -2/+2 | |
| 2020-02-24 | parser: tweak unmatched wording | Mazdak Farrokhzad | -3/+3 | |
| 2020-02-13 | parser: misc small item related improvements & cleanups. | Mazdak Farrokhzad | -2/+2 | |
| 2020-02-13 | parser: introduce `parse_item_kind` as central `ItemInfo` logic. | Mazdak Farrokhzad | -5/+12 | |
| this also extracts macro item parsers. | ||||
| 2019-10-29 | Change E0741 into E0742 | Guillaume Gomez | -2/+2 | |
| 2019-10-29 | Update ui tests | Guillaume Gomez | -2/+3 | |
| 2019-10-24 | Increase spacing for suggestions in diagnostics | Esteban Küber | -0/+6 | |
| Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages. | ||||
| 2019-07-17 | normalize use of backticks in compiler messages for librustc/lint | Samy Kacimi | -1/+1 | |
| https://github.com/rust-lang/rust/issues/60532 | ||||
| 2019-05-04 | Rollup merge of #60429 - estebank:pub-path, r=michaelwoerister | Mazdak Farrokhzad | -4/+17 | |
| Account for paths in incorrect pub qualifier help Handle case where incorrect pub qualifier with a mod path is used and provide the same help given for all other incorrect qualifiers by making the `pub(crate)` parse check more specific. | ||||
| 2019-05-02 | Rollup merge of #59634 - DevQps:explain-E0704, r=estebank | Mazdak Farrokhzad | -0/+1 | |
| Added an explanation for the E0704 error. # Description Adds an explanation on the E0704 error. I tried to stick as closely to the message that the compiler generates. It's the first time I am fixing error messages here, so if there is something I did wrong or should improve, please let me know. closes #55398 | ||||
| 2019-05-01 | Added the E0704 error with a link to the Rust reference. | Christian | -0/+1 | |
| 2019-04-30 | Account for paths in incorrect pub qualifier help | Esteban Küber | -4/+17 | |
| 2019-04-19 | Remove assumption from recovery code | Esteban Küber | -0/+16 | |
| 2019-04-18 | hide `--explain` hint if error has no extended info | Andy Russell | -1/+0 | |
| 2019-03-11 | Update tests | Vadim Petrochenkov | -11/+11 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -139/+19 | |
| 2018-11-30 | Use appropriate terminology based on heuristic | Esteban Küber | -16/+34 | |
| 2018-11-30 | Suggest an appropriate token when encountering `pub Ident<'a>` | Esteban Küber | -0/+47 | |
| 2018-08-14 | Merged migrated compile-fail tests and ui tests. Fixes #46841. | David Wood | -0/+210 | |
| 2018-06-30 | in which the private/restricted-in-public error messaging gets specific | Zack M. Davis | -0/+68 | |
| April 2016's Issue #33174 called out the E0446 diagnostics as confusing. While adding the name of the restricted type to the message (548e681f) clarified matters somewhat, Esteban Küber pointed out that we could stand to place a secondary span on the restricted type. Here, we differentiate between crate-visible, truly private, and otherwise restricted types, and place a secondary span specifically on the visibility modifier of the restricted type's declaration (which we can do now that HIR visibilities have spans!). At long last, this resolves #33174. | ||||
| 2018-06-19 | Update error code numbers | Esteban Küber | -5/+5 | |
| 2018-06-19 | Add code to incorrect `pub` restriction error | Esteban Küber | -4/+5 | |
| 2018-02-26 | Update UI tests | Vadim Petrochenkov | -8/+8 | |
| 2018-01-07 | `struct` pattern parsing and diagnostic tweaks | Esteban Küber | -2/+2 | |
| - Recover from struct parse error on match and point out missing match body. - Point at struct when finding non-identifier while parsing its fields. - Add label to "expected identifier, found {}" error. | ||||
| 2017-12-01 | Auto merge of #45997 - estebank:pub-ident, r=nikomatsakis | bors | -1/+1 | |
| Account for missing keyword in fn/struct definition Fix #38911. | ||||
| 2017-11-24 | Do not attemt to continue parsing after `pub ident` | Esteban Küber | -1/+1 | |
| Try to identify the following code in order to provide better diagnostics, but return the error to bail out early during the parse. | ||||
| 2017-11-24 | Merge cfail and ui tests into ui tests | Oliver Schneider | -16/+16 | |
| 2017-07-02 | Revert "Change error count messages" | Ariel Ben-Yehuda | -4/+4 | |
| This reverts commit 5558c64f33446225739c1153b43d2e309bb4f50e. | ||||
| 2017-05-24 | Change error count messages | Michael Kohl | -4/+4 | |
| See #33525 for details. | ||||
| 2017-04-25 | Rebase and address comments | Oliver Schneider | -4/+4 | |
| 2017-04-25 | Address PR comments | Oliver Schneider | -4/+4 | |
| 2017-04-25 | Update affected tests | Oliver Schneider | -14/+23 | |
| 2017-03-22 | Add diagnostic for incorrect `pub (restriction)` | Esteban Küber | -0/+155 | |
| Given the following statement ```rust pub (a) fn afn() {} ``` Provide the following diagnostic: ```rust error: incorrect restriction in `pub` --> file.rs:15:1 | 15 | pub (a) fn afn() {} | ^^^^^^^ | = help: some valid visibility restrictions are: `pub(crate)`: visible only on the current crate `pub(super)`: visible only in the current module's parent `pub(in path::to::module)`: visible only on the specified path help: to make this visible only to module `a`, add `in` before the path: | pub (in a) fn afn() {} ``` Remove cruft from old `pub(path)` syntax. | ||||
