rust/tests/ui/trait-bounds/maybe-bound-has-path-args.rs

trait Trait {}

fn test<T: ?self::<i32>::Trait>() {}
//~^ ERROR type arguments are not allowed on module `maybe_bound_has_path_args`
//~| ERROR bound modifier `?` can only be applied to `Sized`

fn main() {}
Actually do validation for poly trait refs with ? modifier 2024-10-30 02:28:37 +00:00			`trait Trait {}`

			`fn test<T: ?self::<i32>::Trait>() {}`
Store resolution for self and crate root module segments 2024-10-27 00:16:44 +00:00			//~^ ERROR type arguments are not allowed on module `maybe_bound_has_path_args`
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`
Actually do validation for poly trait refs with ? modifier 2024-10-30 02:28:37 +00:00
			`fn main() {}`