| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -13/+0 | |
| 2021-01-23 | Permit mutable references in all const contexts | oli | -3/+4 | |
| 2020-09-29 | Bless tests | Dylan MacKenzie | -2/+2 | |
| 2020-09-07 | Add CONST_ITEM_MUTATION lint | Aaron Hill | -0/+2 | |
| Fixes #74053 Fixes #55721 This PR adds a new lint `CONST_ITEM_MUTATION`. Given an item `const FOO: SomeType = ..`, this lint fires on: * Attempting to write directly to a field (`FOO.field = some_val`) or array entry (`FOO.array_field[0] = val`) * Taking a mutable reference to the `const` item (`&mut FOO`), including through an autoderef `FOO.some_mut_self_method()` The lint message explains that since each use of a constant creates a new temporary, the original `const` item will not be modified. | ||||
| 2020-06-19 | add new error code | Christian Poveda | -3/+3 | |
| 2020-06-19 | update diagnostics for &mut in constants | Christian Poveda | -3/+3 | |
| 2019-12-02 | Correct other tests related to const_mut_refs | Christian Poveda | -0/+10 | |
| 2019-11-27 | Remove test for unused error code | Dylan MacKenzie | -9/+0 | |
| This error code is never emitted, and the contents of this test are identical to that of `E0017.rs`. | ||||
| 2019-11-12 | check-consts remove cannot mutate statics in initializer of another static error | Santiago Pastorino | -1/+0 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -10/+0 | |
| 2018-11-19 | Also catch static mutation at evaluation time | Oliver Scherer | -0/+1 | |
| 2018-02-08 | Move some E0XXX to `ui` | Esteban Küber | -0/+19 | |
