rust/tests/ui/try-block, branch perf-tmp

replace `//@ compile-flags: --edition` with `//@ edition`

2025-04-10T07:56:37+00:00

Don't mention `FromResidual` on bad `?`

2025-02-18T17:34:16+00:00

Unless `try_trait_v2` is enabled, don't mention that `FromResidual` isn't implemented for a specific type when the implicit `From` conversion of a `?` fails. For the end user on stable, `?` might as well be a compiler intrinsic, so we remove that note to avoid further confusion and allowing other parts of the error to be more prominent. ``` error[E0277]: `?` couldn't convert the error to `u8` --> $DIR/bad-interconversion.rs:4:20 | LL | fn result_to_result() -> Result { | --------------- expected `u8` because of this LL | Ok(Err(123_i32)?) | ------------^ the trait `From` is not implemented for `u8` | | | this can't be annotated with `?` because it has type `Result<_, i32>` | = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait = help: the following other types implement trait `From`: `u8` implements `From` `u8` implements `From` ```

Add trait diff highlighting logic and use it in E0277

2024-11-02T03:08:04+00:00

When a trait is not implemented for a type, but there *is* an `impl` for another type or different trait params, we format the output to use highlighting in the same way that E0308 does for types. The logic accounts for 3 cases: - When both the type and trait in the expected predicate and the candidate are different - When only the types are different - When only the trait generic params are different For each case, we use slightly different formatting and wording.

Remove detail from label/note that is already available in other note

2024-10-29T16:26:57+00:00

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> = IsCopy { t: None }; | ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `NotCopy` | = note: required for `Option` to implement `Copy` note: required by a bound in `IsCopy` --> $DIR/wf-static-type.rs:7:17 | LL | struct IsCopy { 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> = IsCopy { t: None }; | ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `NotCopy`, which is required by `Option: Copy` | = note: required for `Option` to implement `Copy` note: required by a bound in `IsCopy` --> $DIR/wf-static-type.rs:7:17 | LL | struct IsCopy { t: T } | ^^^^ required by this bound in `IsCopy` ```

Stop inverting expectation in normalization errors

2024-10-16T17:44:56+00:00

Peel off explicit (or implicit) deref before suggesting clone on move error in borrowck

2024-07-26T18:41:56+00:00

Use shorter span for float literal suggestion

2024-07-04T05:19:35+00:00

Fix accuracy of `T: Clone` check in suggestion

2024-04-11T16:41:41+00:00

[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives

2024-02-16T20:02:50+00:00

add test for try-block-in-match-arm

2024-02-01T18:36:34+00:00

This is noted as an implementation concern under the tracking issue for `?` and `try` blocks. (Issue 31436)