| Age | Commit message (Expand) | Author | Lines |
|---|---|---|---|
| 2025-06-07 | const-eval error: always say in which item the error occurred | Ralf Jung | -1/+1 |
| 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 | -1/+0 |
| 2025-02-28 | Shorten span of panic failures in const context | Esteban Küber | -10/+6 |
| 2025-01-18 | const-eval: detect more pointers as definitely not-null | Ralf Jung | -1/+1 |
| 2024-11-16 | stabilize const_ptr_is_null | Ralf Jung | -1/+1 |
| 2024-11-05 | add const_eval_select macro to reduce redundancy | Ralf Jung | -2/+2 |
| 2024-09-08 | const: make ptr.is_null() stop execution on ambiguity | Ralf Jung | -0/+19 |
