7 Commits

Author	SHA1	Message	Date
Ralf Jung	17946c22b1	const-eval error: always say in which item the error occurred ... also adjust the wording a little so that we don't say "the error occurred here" for two different spans	2025-06-07 13:42:30 +02:00
Oli Scherer	020216c31c	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
Oli Scherer	b331b8b96d	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
Esteban Küber	cc492edc9d	Tweak unevaluated constant in pattern error ... Silence errors that are implied by the errors in the `const` item definition. Add a primary span label.	2024-12-04 20:29:35 +00:00
Esteban Küber	c6205055e0	On const pattern errors, point at the const item definition ... 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"), | ^^^^ ```	2024-12-04 20:29:35 +00:00
Camille GILLOT	05082f57af	Perform match checking on THIR.	2023-04-03 15:59:21 +00:00
Albert Larsan	cf2dff2b1e	Move /src/test to /tests	2023-01-11 09:32:08 +00:00