Sasha Pourcelot 5c4b61b4b4 don't uppercase error messages ... 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 😅. 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-09-03 15:24:49 +02:00
..
allowed_slices.rs	terminology: allocated object → allocation	2025-05-31 22:49:14 +02:00
forbidden_slices.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
forbidden_slices.stderr	don't uppercase error messages	2025-09-03 15:24:49 +02:00
out_of_bounds_read.rs	Use the informative error as the main const eval error message	2025-06-02 15:37:15 +00:00
out_of_bounds_read.stderr	const-eval error: always say in which item the error occurred	2025-06-07 13:42:30 +02:00
pointer-address-stability.rs	cleaned up some tests	2025-07-05 01:54:04 +05:00