| Age | Commit message (Expand) | Author | Lines |
|---|---|---|---|
| 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-03-14 | Do not suggest using `-Zmacro-backtrace` for builtin macros | Esteban Küber | -2/+0 |
| 2025-02-28 | Shorten span of panic failures in const context | Esteban Küber | -1/+1 |
| 2024-04-24 | Fix tests and bless | Gary Guo | -3/+3 |
| 2024-03-14 | preserve span when evaluating mir::ConstOperand | Ralf Jung | -0/+6 |
| 2023-11-24 | Show number in error message even for one error | Nilstrieb | -1/+1 |
| 2023-08-18 | Add a test to check that inline const is in required_consts | Gary Guo | -0/+11 |
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |