rust/tests/ui/enum-discriminant, branch perf-tmphttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=perf-tmp2025-08-10T19:43:52+00:00Rollup merge of #144553 - Oneirical:uncountable-integer-4, r=jieyouxu2025-08-10T19:43:52+00:00Jacob Prattjacob@jhpratt.dev2025-08-10T19:43:52+00:00urn:sha1:5bd4e832d3608a4b06e3bc0b0bf348e664e961ec
Rehome 32 `tests/ui/issues/` tests to other subdirectories under `tests/ui/`
rust-lang/rust#143902 divided into smaller, easier to review chunks.
Part of rust-lang/rust#133895
Methodology:
1. Refer to the previously written `tests/ui/SUMMARY.md`
2. Find an appropriate category for the test, using the original issue thread and the test contents.
3. Add the issue URL at the bottom (not at the top, as that would mess up stderr line numbers)
4. Rename the tests to make their purpose clearer
Inspired by the methodology that `@Kivooeo` was using.
r? `@jieyouxu`
Rehome tests/ui/issues/ tests [4/?]2025-08-10T15:54:15+00:00Oneiricalmanchot@videotron.ca2025-07-13T20:39:45+00:00urn:sha1:aa543963c68061d9ca46037071d66a028626ff3fPick the largest niche even if the largest niche is wrapped around2025-07-29T14:08:15+00:00Oli Scherergithub333195615777966@oli-obk.de2025-07-24T10:19:20+00:00urn:sha1:75bdbf25e39f073b35eadedcf575affac7762a86Add regression test2025-07-28T10:29:02+00:00Oli Scherergithub333195615777966@oli-obk.de2025-07-24T08:07:56+00:00urn:sha1:45b0c8d03e627d55f814a4cd03b90c5068664ac8Remove dead code and extend test coverage and diagnostics around it2025-07-24T10:21:20+00:00Oli Scherergithub333195615777966@oli-obk.de2025-07-24T08:15:03+00:00urn:sha1:e44a7386c27f821515804fa90ed39ca1e931f8de
We lost the following comment during refactorings:
The current code for niche-filling relies on variant indices instead of actual discriminants, so enums with explicit discriminants (RFC 2363) would misbehave.
Unconditionally run `check_item_type` on all items2025-06-30T08:06:08+00:00Oli Scherergithub333195615777966@oli-obk.de2025-06-04T08:46:49+00:00urn:sha1:9b5d57d0a9d8ba75fd1602f62d0bfd9f2f6acd1econst-eval error: always say in which item the error occurred2025-06-07T11:42:30+00:00Ralf Jungpost@ralfj.de2025-06-07T09:32:09+00:00urn: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 place2025-06-02T15:37:15+00:00Oli Scherergithub333195615777966@oli-obk.de2025-05-30T14:06:35+00:00urn:sha1:020216c31c1e4f1f56a689df8f04580504354613Use the informative error as the main const eval error message2025-06-02T15:37:15+00:00Oli Scherergithub333195615777966@oli-obk.de2025-05-28T10:29:08+00:00urn:sha1:b331b8b96d86a6433df957a3cc49ed51f3656135Stabilise `repr128`2025-05-28T14:14:34+00:00beetreesb@beetr.ee2025-03-09T19:03:12+00:00urn:sha1:467eeabbb5e876abc6bf552670199695172ad07a