rust/tests/ui/generic-const-items/trivially-unsatisfied-bounds-0.stderr, branch try-perf https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try-perf 2025-06-07T11:42:30+00:00 const-eval error: always say in which item the error occurred 2025-06-07T11:42:30+00:00 Ralf Jung post@ralfj.de 2025-06-07T09:32:09+00:00 urn:sha1:17946c22b1d7abd2dd990bf6998c8491b534fe62 also adjust the wording a little so that we don't say "the error occurred here" for two different spans Clarify why we are talking about a failed const eval at a random place 2025-06-02T15:37:15+00:00 Oli Scherer github333195615777966@oli-obk.de 2025-05-30T14:06:35+00:00 urn:sha1:020216c31c1e4f1f56a689df8f04580504354613 Use the informative error as the main const eval error message 2025-06-02T15:37:15+00:00 Oli Scherer github333195615777966@oli-obk.de 2025-05-28T10:29:08+00:00 urn:sha1:b331b8b96d86a6433df957a3cc49ed51f3656135 Always evaluate free constants and statics, even if previous errors occurred 2024-02-19T22:11:13+00:00 Oli Scherer git-spam-no-reply9815368754983@oli-obk.de 2024-02-14T12:28:07+00:00 urn:sha1:90626979170da2d6c5ec1622b3d7a9512df9eb71 Show number in error message even for one error 2023-11-24T18:15:52+00:00 Nilstrieb 48135649+Nilstrieb@users.noreply.github.com 2023-11-21T15:44:16+00:00 urn:sha1:41e8d152dc5abb5a706999ada8b059d3420af8f3 Co-authored-by: Adrian <adrian.iosdev@gmail.com> Add UI tests for generic const items 2023-07-28T20:23:20+00:00 León Orell Valerian Liehr me@fmease.dev 2023-07-10T01:10:03+00:00 urn:sha1:6636916b666d067277ee31c1eab1970912b6eb8a