diff options
| author | León Orell Valerian Liehr <me@fmease.dev> | 2025-07-18 12:24:56 +0200 |
|---|---|---|
| committer | León Orell Valerian Liehr <me@fmease.dev> | 2025-07-18 12:24:56 +0200 |
| commit | cdc3d701cb4ff37e9d0c96c1c68b2e8789c19441 (patch) | |
| tree | 508b765b23ec32b6988c64e88f6f373e86313624 /tests/ui/enum/nested-enum.rs | |
| parent | 879f62bb3c23b7a90ac71bb217056fd49ff8dafb (diff) | |
| download | rust-cdc3d701cb4ff37e9d0c96c1c68b2e8789c19441.tar.gz rust-cdc3d701cb4ff37e9d0c96c1c68b2e8789c19441.zip | |
Don't reject *multiple* relaxed bounds, reject *duplicate* ones.
Having multiple relaxed bounds like `?Sized + ?Iterator` is actually *fine*. We actually want to reject *duplicate* relaxed bounds like `?Sized + ?Sized` because these most certainly represent a user error. Note that this doesn't mean that we accept more code because a bound like `?Iterator` is still invalid as it's not relaxing a *default* trait and the only way to define / use more default bounds is under the experimental and internal feature `more_maybe_bounds` plus `lang_items` plus unstable flag `-Zexperimental-default-bounds` (historical context: for the longest time, bounds like `?Iterator` were actually allowed and lead to a hard warning). Ultimately, this simply *reframes* the diagnostic. The scope of `more_maybe_bounds` / `-Zexperimental-default-bounds` remains unchanged as well.
Diffstat (limited to 'tests/ui/enum/nested-enum.rs')
0 files changed, 0 insertions, 0 deletions
