| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2025-06-07 | const-eval error: always say in which item the error occurred | Ralf Jung | -1/+1 | |
| 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 | -1/+1 | |
| 2025-06-02 | Use the informative error as the main const eval error message | Oli Scherer | -2/+2 | |
| 2025-04-30 | compiletest: Make diagnostic kind mandatory on line annotations | Vadim Petrochenkov | -3/+3 | |
| 2023-11-24 | Show number in error message even for one error | Nilstrieb | -1/+1 | |
| Co-authored-by: Adrian <adrian.iosdev@gmail.com> | ||||
| 2023-09-14 | don't point at const usage site for resolution-time errors | Ralf Jung | -3/+3 | |
| also share the code that emits the actual error | ||||
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -0/+27 | |
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |