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
Vadim Petrochenkov	20faf8532b	compiletest: Make diagnostic kind mandatory on line annotations	2025-04-30 10:44:24 +03:00
Oli Scherer	9062697917	Always evaluate free constants and statics, even if previous errors occurred	2024-02-19 22:11:13 +00:00
Nilstrieb	41e8d152dc	Show number in error message even for one error ... Co-authored-by: Adrian <adrian.iosdev@gmail.com>	2023-11-24 19:15:52 +01:00
Albert Larsan	cf2dff2b1e	Move /src/test to /tests	2023-01-11 09:32:08 +00:00