rust/tests/ui/sized/relaxing-default-bound-error-37534.rs

struct Foo<T: ?Hash> {}
//~^ ERROR expected trait, found derive macro `Hash`
//~| ERROR bound modifier `?` can only be applied to `Sized`

fn main() {}

// https://github.com/rust-lang/rust/issues/37534
Improve some diagnostics around `?Trait` bounds 2023-10-30 17:47:07 +00:00			`struct Foo<T: ?Hash> {}`
resolve: Attempt to resolve unresolved paths in macro namespace 2019-07-15 03:28:17 +03:00			//~^ ERROR expected trait, found derive macro `Hash`
Reword diagnostic about relaxing non-`Sized` bound * The phrasing "only does something for" made sense back when this diagnostic was a (hard) warning. Now however, it's simply a hard error and thus completely rules out "doing something". * The primary message was way too long * The new wording more closely mirrors the wording we use for applying other bound modifiers (like `const` and `async`) to incompatible traits. * "all other traits are not bound by default" is no longer accurate under Sized Hierarchy. E.g., traits and assoc tys are (currently) bounded by `MetaSized` by default but can't be relaxed using `?MetaSized` (instead, you relax it by adding `PointeeSized`). * I've decided against adding any diagnositic notes or suggestions for now like "trait `Trait` can't be relaxed as it's not bound by default" which would be incorrect for `MetaSized` and assoc tys as mentioned above) or "consider changing `?MetaSized` to `PointeeSized`" as the Sized Hierarchy impl is still WIP) 2025-06-19 18:41:57 +02:00			//~\| ERROR bound modifier `?` can only be applied to `Sized`
Fix ICE when querying DefId on Def::Err. 2016-11-03 14:55:35 -06:00
Improve some diagnostics around `?Trait` bounds 2023-10-30 17:47:07 +00:00			`fn main() {}`
Rehome tests/ui/issues/ tests [1/?] 2025-07-13 15:56:27 -04:00
			`// https://github.com/rust-lang/rust/issues/37534`