Esteban Küber 5b54286640 Remove detail from label/note that is already available in other note ... Remove the "which is required by `{root_obligation}`" post-script in "the trait `X` is not implemented for `Y`" explanation in E0277. This information is already conveyed in the notes explaining requirements, making it redundant while making the text (particularly in labels) harder to read. ``` error[E0277]: the trait bound `NotCopy: Copy` is not satisfied --> $DIR/wf-static-type.rs:10:13 | LL | static FOO: IsCopy<Option<NotCopy>> = IsCopy { t: None }; | ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `NotCopy` | = note: required for `Option<NotCopy>` to implement `Copy` note: required by a bound in `IsCopy` --> $DIR/wf-static-type.rs:7:17 | LL | struct IsCopy<T:Copy> { t: T } | ^^^^ required by this bound in `IsCopy` ``` vs the prior ``` error[E0277]: the trait bound `NotCopy: Copy` is not satisfied --> $DIR/wf-static-type.rs:10:13 | LL | static FOO: IsCopy<Option<NotCopy>> = IsCopy { t: None }; | ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `NotCopy`, which is required by `Option<NotCopy>: Copy` | = note: required for `Option<NotCopy>` to implement `Copy` note: required by a bound in `IsCopy` --> $DIR/wf-static-type.rs:7:17 | LL | struct IsCopy<T:Copy> { t: T } | ^^^^ required by this bound in `IsCopy` ```		2024-10-29 16:26:57 +00:00
..
for-c-in-str.rs
for-c-in-str.stderr
for-else-err.rs
for-else-err.stderr
for-else-let-else-err.rs
for-else-let-else-err.stderr
for-expn.rs
for-expn.stderr
for-loop-bogosity.rs
for-loop-bogosity.stderr
for-loop-refutable-pattern-error-message.rs
for-loop-refutable-pattern-error-message.stderr
for-loop-type-error.rs
for-loop-type-error.stderr
for-loop-unconstrained-element-type.rs
for-loop-unconstrained-element-type.stderr
issue-20605.current.stderr
issue-20605.next.stderr
issue-20605.rs