about summary refs log tree commit diff
path: root/tests/ui/issues/issue-37534.rs
AgeCommit message (Collapse)AuthorLines
2025-07-24Rehome tests/ui/issues/ tests [1/?]Oneirical-5/+0
2025-07-18Reword diagnostic about relaxing non-`Sized` boundLeón Orell Valerian Liehr-1/+1
* 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-02-11Reject `impl Trait` bounds in various places where we unconditionally warned ↵Oli Scherer-1/+1
since 1.0
2024-10-30Actually do validation for poly trait refs with ? modifierMichael Goulet-2/+1
2023-10-30Improve some diagnostics around `?Trait` boundsOli Scherer-3/+3
2023-01-11Move /src/test to /testsAlbert Larsan-0/+6