rust/tests/ui/pattern/deref-patterns, branch automation/bors/try

fix: Add col separator before secondary messages with no source

2025-08-26T21:15:17+00:00

On E0277, point at type that doesn't implement bound

2025-08-22T17:55:15+00:00

When encountering an unmet trait bound, point at local type that doesn't implement the trait: ``` error[E0277]: the trait bound `Bar: Foo` is not satisfied --> $DIR/issue-64855.rs:9:19 | LL | pub struct Bar(::Type) where Self: ; | ^^^^^^^^^^^^^^^^^^^ unsatisfied trait bound | help: the trait `Foo` is not implemented for `Bar` --> $DIR/issue-64855.rs:9:1 | LL | pub struct Bar(::Type) where Self: ; | ^^^^^^^^^^^^^^^^^ ```

In rustc_pattern_analysis, put `true` witnesses before `false` witnesses

2025-07-27T23:01:39+00:00

In rustc it doesn't really matter what the order of the witnesses is, but I'm planning to use the witnesses for implementing the "add missing match arms" assist in rust-analyzer, and there `true` before `false` is the natural order (like `Some` before `None`), and also what the current assist does. The current order doesn't seem to be intentional; the code was created when bool ctors became their own thing, not just int ctors, but for integer, 0 before 1 is indeed the natural order.

error early when mixing deref patterns with normal constructors

2025-05-07T01:53:55+00:00

Without adding proper support for mixed exhaustiveness, mixing deref patterns with normal constructors would either violate `ConstructorSet::split`'s invariant 4 or 7. We'd either be ignoring rows with normal constructors or we'd have problems in unspecialization from non-disjoint constructors. Checking mixed exhaustivenss similarly to how unions are currently checked should work, but the diagnostics for unions are confusing. Since mixing deref patterns with normal constructors is pretty niche (currently it only makes sense for `Cow`), emitting an error lets us avoid committing to supporting mixed exhaustiveness without a good answer for the diagnostics.

add exhaustiveness/usefulness tests for deref patterns

2025-05-07T01:53:55+00:00

let deref patterns participate in usefulness/exhaustiveness

2025-05-07T01:53:55+00:00

This does not yet handle the case of mixed deref patterns with normal constructors; it'll ICE in `Constructor::is_covered_by`. That'll be fixed in a later commit.

always peel `&mut`, to allow matching on `&mut str`

2025-05-05T11:29:33+00:00

match ergonomics for string and byte string literal patterns

2025-05-05T11:10:49+00:00

compiletest: Make diagnostic kind mandatory on line annotations

2025-04-30T07:44:24+00:00

Test partial moves via deref pats

2025-04-27T15:25:15+00:00