rust/tests/ui/consts/const-eval/ub-nonnull.stderr, branch automation/bors/tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=automation/bors/try2025-09-24T11:34:33+00:00const-eval: improve and actually test the errors when pointers might be outside the range of a scalar2025-09-24T11:34:33+00:00Ralf Jungpost@ralfj.de2025-09-22T17:46:30+00:00urn:sha1:0a41add6293d76b165968d70f95e7edbbe65fe11don't uppercase error messages2025-09-03T13:24:49+00:00Sasha Pourcelotsasha.pourcelot@protonmail.com2025-09-01T14:47:55+00:00urn: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.
Show the memory of uninit reads2025-07-18T07:47:08+00:00Oli Scherergithub333195615777966@oli-obk.de2025-06-18T12:51:47+00:00urn:sha1:652ba279ecc693d8b4310c40e645a62009f5b0edReport the range of uninit bytes in CTFE errors2025-07-17T20:00:51+00:00Oli Scherergithub333195615777966@oli-obk.de2025-06-18T12:51:47+00:00urn:sha1:12eedafc38b1d3af02c9c15333d0ba2f1aee1253const-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:b331b8b96d86a6433df957a3cc49ed51f3656135Rollup merge of #140521 - RalfJung:oob-error, r=saethlin2025-05-02T17:37:58+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-05-02T17:37:58+00:00urn:sha1:c796ef00f8d3b9a886e482305c4fc3026eb89528
interpret: better error message for out-of-bounds pointer arithmetic and accesses
Fixes https://github.com/rust-lang/rust/issues/93881
r? `@saethlin`
interpret: better error message for out-of-bounds pointer arithmetic and accesses2025-04-30T16:45:41+00:00Ralf Jungpost@ralfj.de2025-04-30T14:52:25+00:00urn:sha1:00f25a8e1cf7d749946a6a9fb7327bf4710c931fcompiletest: Make diagnostic kind mandatory on line annotations2025-04-30T07:44:24+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2025-04-05T16:19:56+00:00urn:sha1:20faf8532b5ddeb636ba3078344b0cad058c8f8a