| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2025-06-07 | const-eval error: always say in which item the error occurred | Ralf Jung | -2/+2 | |
| also adjust the wording a little so that we don't say "the error occurred here" for two different spans | ||||
| 2025-06-02 | Clarify why we are talking about a failed const eval at a random place | Oli Scherer | -2/+2 | |
| 2025-06-02 | Use the informative error as the main const eval error message | Oli Scherer | -5/+5 | |
| 2024-09-15 | also stabilize const_refs_to_cell | Ralf Jung | -2/+2 | |
| 2024-08-17 | make writes_through_immutable_pointer a hard error | Ralf Jung | -47/+7 | |
| 2023-12-07 | compile-time evaluation: emit a lint when a write through an immutable ↵ | Ralf Jung | -0/+55 | |
| pointer occurs | ||||
