https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=perf-tmp 2025-09-26T13:33:48+00:00 2025-09-26T13:33:48+00:00 Guillaume Gomez guillaume1.gomez@gmail.com 2025-09-26T11:59:06+00:00 urn:sha1:a535c7be5444fb6584eecc99f53e6cdb710ff70f 2025-09-13T07:26:02+00:00 Jacob Pratt jacob@jhpratt.dev 2025-09-13T07:26:02+00:00 urn:sha1:82bb6d523bf3b1e6cd8d160565ab18d01640a4dd Rehome 30 `tests/ui/issues/` tests to other subdirectories under `tests/ui/` [#3 of Batch #2] 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` 2025-09-12T18:45:12+00:00 Oneirical manchot@videotron.ca 2025-08-20T18:02:50+00:00 urn:sha1:957fa10d50787a4c6c6d8a35be5af6bd43ba1770 2025-09-03T13:24:49+00:00 Sasha Pourcelot sasha.pourcelot@protonmail.com 2025-09-01T14:47:55+00:00 urn:sha1:5c4b61b4b4b13e408b28ecc91f4f517e78e6b5e7 a more general version of https://github.com/rust-lang/rust/pull/146080. after a bit of hacking in [`fluent.rs`](https://github.com/rust-lang/rust/blob/master/compiler/rustc_fluent_macro/src/fluent.rs), i discovered that i'm not the only one that is bad at following guidelines :sweat_smile:. this pr lowercases the first letter of all the error messages in the codebase. (i did not change things that are traditionally uppercased such as _MIR_, _ABI_ or _C_) i think it's reasonable to run a `@bors try` so all the test suite is checked, as i cannot run some of the tests on my machine. i double checked (and replaced manually) all the old error messages, but better be safe than sorry. in the future i will try to add a check in `x test tidy` that errors if an error message starts with an uppercase letter. 2025-08-31T11:40:34+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-08-31T11:40:34+00:00 urn:sha1:0e28b4201ac8f12cfafe5383f442c7b00f8bdcc6 Make target pointer width in target json an integer r? Noratrieb cc `@RalfJung` (https://github.com/rust-lang/rust/pull/142352/files#r2230380120) try-job: x86_64-rust-for-linux 2025-08-29T10:37:30+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-08-29T10:37:30+00:00 urn:sha1:47f1df5ca35217ca5e21ffd1f1daa3cb623470e2 Rehome 30 `tests/ui/issues/` tests to other subdirectories under `tests/ui/` [#2 of Batch #2] 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` 2025-08-29T10:37:30+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-08-29T10:37:30+00:00 urn:sha1:e15744e7a4095a868cc3d145ae81bd6660247519 Rehome 30 `tests/ui/issues/` tests to other subdirectories under `tests/ui/` [#1 of Batch #2] 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` 2025-08-27T21:44:49+00:00 Waffle Lapkin waffle.lapkin@gmail.com 2025-07-31T17:03:22+00:00 urn:sha1:6a3187af13e59beb00f6eaff8c4c9da19b382d36 2025-08-27T19:06:05+00:00 Oneirical manchot@videotron.ca 2025-08-20T18:02:44+00:00 urn:sha1:2dc4638c4637bf8ddb83577535317dad21abdf6d 2025-08-27T04:23:26+00:00 Oneirical manchot@videotron.ca 2025-08-20T18:02:39+00:00 urn:sha1:2e659f58940a31fa625e88f75f78111ed773f32d