about summary refs log tree commit diff
path: root/tests/ui/const-generics/min_const_generics/invalid-patterns.64bit.stderr
AgeCommit message (Collapse)AuthorLines
2025-09-03don't uppercase error messagesSasha Pourcelot-2/+2
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-07-18Show the memory of uninit readsOli Scherer-0/+8
2025-07-17Report the range of uninit bytes in CTFE errorsOli Scherer-2/+2
2025-06-07const-eval error: always say in which item the error occurredRalf Jung-2/+2
also adjust the wording a little so that we don't say "the error occurred here" for two different spans
2025-06-02Clarify why we are talking about a failed const eval at a random placeOli Scherer-2/+2
2025-06-02Use the informative error as the main const eval error messageOli Scherer-11/+11
2025-04-30compiletest: Make diagnostic kind mandatory on line annotationsVadim Petrochenkov-8/+8
2025-01-09Always take the `Ok` path in `lit_to_const` and produce error constants insteadOli Scherer-24/+24
2023-01-11Move /src/test to /testsAlbert Larsan-0/+62