| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-03-11 | Update tests | Vadim Petrochenkov | -1/+1 | |
| 2019-01-30 | Move privacy checking later in the pipeline and make some passes run in parallel | John Kåre Alsaker | -2/+2 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -1/+1 | |
| 2018-06-30 | in which the private/restricted-in-public error messaging gets specific | Zack M. Davis | -0/+3 | |
| 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-03-14 | update tests | Guillaume Gomez | -1/+1 | |
| 2018-02-26 | Update UI tests | Vadim Petrochenkov | -3/+3 | |
| 2018-02-25 | Update ui tests | Guillaume Gomez | -0/+1 | |
| 2018-02-08 | Move some E0XXX to `ui` | Esteban Küber | -0/+10 | |
