about summary refs log tree commit diff
path: root/tests/ui/const-generics/min_const_generics
AgeCommit message (Collapse)AuthorLines
2025-09-03don't uppercase error messagesSasha Pourcelot-4/+4
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-19bless tests with new lint messagesKarol Zwolak-2/+2
2025-08-06Fortify generic param default checksLeón Orell Valerian Liehr-2/+2
2025-07-25Update ui tests with new macro early erroringGuillaume Gomez-44/+80
2025-07-18Show the memory of uninit readsOli Scherer-0/+16
2025-07-17Report the range of uninit bytes in CTFE errorsOli Scherer-4/+4
2025-06-18Rollup merge of #141610 - BoxyUwU:stabilize_generic_arg_infer, ↵Jakub Beránek-1/+0
r=lcnr,traviscross Stabilize `feature(generic_arg_infer)` Fixes rust-lang/rust#85077 r? lcnr cc ````@rust-lang/project-const-generics````
2025-06-12Rollup merge of #142157 - Enselic:trivial-anon-const-use-cases, ↵Matthias Krüger-4/+4
r=compiler-errors rustc_resolve: Improve `resolve_const_param_in_non_trivial_anon_const` wording In some contexts, const expressions are OK. Add a `here` to the error message to clarify this. Closes rust-lang/rust#79429 which has 15 x 👍
2025-06-11stabilize gaiBoxy-1/+0
2025-06-07const-eval error: always say in which item the error occurredRalf Jung-4/+4
also adjust the wording a little so that we don't say "the error occurred here" for two different spans
2025-06-07rustc_resolve: Improve `resolve_const_param_in_non_trivial_anon_const` wordingMartin Nordholts-4/+4
In some contexts, const expressions are OK. Add a `here` to the error message to clarify this.
2025-06-02Clarify why we are talking about a failed const eval at a random placeOli Scherer-4/+4
2025-06-02Use the informative error as the main const eval error messageOli Scherer-28/+26
2025-04-30compiletest: Make diagnostic kind mandatory on line annotationsVadim Petrochenkov-18/+20
2025-01-09Always take the `Ok` path in `lit_to_const` and produce error constants insteadOli Scherer-48/+48
2024-12-18add testslcnr-0/+3
2024-12-17add testslcnr-0/+23
2024-09-29fix(hir_analysis/wfcheck): don't leak {type error}Barrett Ray-7/+7
avoid `{type error}` being leaked in user-facing messages, particularly when using the `adt_const_params` feature
2024-07-17Split part of `adt_const_params` into `unsized_const_params`Boxy-0/+4
2024-07-09Automatically taint when reporting errors from ItemCtxtOli Scherer-82/+21
2024-06-26Automatically taint InferCtxt when errors are emittedOli Scherer-22/+83
2024-03-20Bless test fallout (duplicate diagnostics)Michael Goulet-8/+17
2024-03-18Provide structured suggestion for `#![feature(foo)]`Esteban Küber-6/+24
``` error: `S2<'_>` is forbidden as the type of a const generic parameter --> $DIR/lifetime-in-const-param.rs:5:23 | LL | struct S<'a, const N: S2>(&'a ()); | ^^ | = note: the only supported types are integers, `bool` and `char` help: add `#![feature(adt_const_params)]` to the crate attributes to enable more complex and user defined types | LL + #![feature(adt_const_params)] | ``` Fix #55941.
2024-02-17Allow newly added non_local_definitions lint in testsUrgau-0/+2
2024-02-16[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives许杰友 Jieyou Xu (Joe)-10/+10
2024-01-09Avoid silencing relevant follow-up errorsOli Scherer-5/+26
2023-11-30generic_const_exprs: suggest to add the feature, not use itRalf Jung-10/+10
2023-11-24Show number in error message even for one errorNilstrieb-4/+4
Co-authored-by: Adrian <adrian.iosdev@gmail.com>
2023-09-28make adt_const_params feature suggestion more consistent with others and ↵asquared31415-7/+6
only suggest it when the type can probably work
2023-05-05improve diagnostics and bless testsBoxy-11/+10
2023-01-20preserve delim spans during `macro_rules!` expansion if ableLukas Markeffsky-14/+9
2023-01-11Move /src/test to /testsAlbert Larsan-0/+1249