rust/tests/ui/array-slice-vec, branch master https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=master 2025-09-26T13:33:48+00:00 Ignore more failing ui tests for GCC backend 2025-09-26T13:33:48+00:00 Guillaume Gomez guillaume1.gomez@gmail.com 2025-09-26T11:59:06+00:00 urn:sha1:a535c7be5444fb6584eecc99f53e6cdb710ff70f Add test batch 2 2025-08-27T19:06:05+00:00 Oneirical manchot@videotron.ca 2025-08-20T18:02:44+00:00 urn:sha1:2dc4638c4637bf8ddb83577535317dad21abdf6d Rollup merge of #144983 - Oneirical:uncountable-integer, r=jieyouxu 2025-08-19T11:42:06+00:00 许杰友 Jieyou Xu (Joe) 39484203+jieyouxu@users.noreply.github.com 2025-08-19T11:42:06+00:00 urn:sha1:2d058708975587e2ef189489e34b7c78efcfcc42 Rehome 37 `tests/ui/issues/` tests to other subdirectories under `tests/ui/` 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 [5/?] 2025-08-17T17:01:02+00:00 Oneirical manchot@videotron.ca 2025-07-13T20:56:31+00:00 urn:sha1:75e0263af9ca27eac2c922538582deec764d1e7b overhaul `&mut` suggestions in borrowck errors 2025-08-16T14:34:17+00:00 Deadbeef ent3rm4n@gmail.com 2025-08-06T14:37:14+00:00 urn:sha1:4335405fa7c709b2733c6121fbf4bc0d8e291dcc Rehome tests/ui/issues/ tests [3/?] 2025-08-04T20:43:53+00:00 Oneirical manchot@videotron.ca 2025-07-13T20:25:27+00:00 urn:sha1:7196d8cd661b875401126a81641d2effc40b3d85 stabilize gai 2025-06-11T14:30:15+00:00 Boxy rust@boxyuwu.dev 2025-06-11T14:30:15+00:00 urn:sha1:fe04ae7fafab80cebd01ce9c199248556ec3654f 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