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
..
collect-in-called-fn.noopt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-called-fn.opt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-called-fn.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
collect-in-dead-closure.noopt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-closure.opt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-closure.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
collect-in-dead-drop.noopt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-drop.opt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-drop.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
collect-in-dead-fn-behind-assoc-type.noopt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-fn-behind-assoc-type.opt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-fn-behind-assoc-type.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
collect-in-dead-fn-behind-generic.noopt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-fn-behind-generic.opt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-fn-behind-generic.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
collect-in-dead-fn-behind-opaque-type.noopt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-fn-behind-opaque-type.opt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-fn-behind-opaque-type.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
collect-in-dead-fn.noopt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-fn.opt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-fn.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
collect-in-dead-fnptr-in-const.noopt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-fnptr-in-const.opt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-fnptr-in-const.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
collect-in-dead-fnptr.noopt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-fnptr.opt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-fnptr.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
collect-in-dead-forget.rs	explicitly set opt-level=0	2024-03-20 11:07:12 +01:00
collect-in-dead-move.noopt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-move.opt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-move.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
collect-in-dead-vtable.noopt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-vtable.opt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-dead-vtable.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
collect-in-promoted-const.noopt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-promoted-const.opt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
collect-in-promoted-const.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
interpret-in-const-called-fn.noopt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
interpret-in-const-called-fn.opt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
interpret-in-const-called-fn.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
interpret-in-promoted.noopt.stderr	const-eval error: always say in which item the error occurred	2025-06-07 13:42:30 +02:00
interpret-in-promoted.opt.stderr	const-eval error: always say in which item the error occurred	2025-06-07 13:42:30 +02:00
interpret-in-promoted.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
interpret-in-static.noopt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
interpret-in-static.opt.stderr	Clarify why we are talking about a failed const eval at a random place	2025-06-02 15:37:15 +00:00
interpret-in-static.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00