mirror of
https://github.com/rust-lang/rust.git
synced 2025-10-04 11:17:04 +00:00
879f62bb3c
* 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)
13 lines
336 B
Rust
13 lines
336 B
Rust
trait HasAssoc {
|
|
type Assoc;
|
|
}
|
|
fn hasassoc<T: ?HasAssoc<Assoc = ()>>() {}
|
|
//~^ ERROR bound modifier `?` can only be applied to `Sized`
|
|
|
|
trait NoAssoc {}
|
|
fn noassoc<T: ?NoAssoc<Missing = ()>>() {}
|
|
//~^ ERROR bound modifier `?` can only be applied to `Sized`
|
|
//~| ERROR associated type `Missing` not found for `NoAssoc`
|
|
|
|
fn main() {}
|