| 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 | |
| 2024-12-04 | Tweak unevaluated constant in pattern error | Esteban Küber | -10/+1 | |
| Silence errors that are implied by the errors in the `const` item definition. Add a primary span label. | ||||
| 2024-12-04 | On `const` pattern errors, point at the `const` item definition | Esteban Küber | -0/+3 | |
| Centralize emitting an error in `const_to_pat` so that all errors from that evaluating a `const` in a pattern can add addditional information. With this, now point at the `const` item's definition: ``` error[E0158]: constant pattern depends on a generic parameter --> $DIR/associated-const-type-parameter-pattern.rs:20:9 | LL | pub trait Foo { | ------------- LL | const X: EFoo; | ------------- constant defined here ... LL | A::X => println!("A::X"), | ^^^^ ``` | ||||
| 2023-04-03 | Perform match checking on THIR. | Camille GILLOT | -7/+1 | |
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -0/+21 | |
