Misleading label & invalid suggestion on (multi-segment) assoc const of wrong type in pattern

Given

struct Owner;
impl Owner { const K: &str = ""; }

fn scope(source: std::borrow::Cow<'_, str>) {
    match source {
        Owner::K => {}
        _ => {}
    }
}

rustc emits the following:

error[E0308]: mismatched types
 --> src/lib.rs:6:9
  |
2 | impl Owner { const K: &str = ""; }
  |              ------------- associated constant defined here
...
5 |     match source {
  |           ------ this expression has type `Cow<'_, str>`
6 |         Owner::K => {}
  |         ^^^^^^^^
  |         |
  |         expected `Cow<'_, str>`, found `&str`
  |         `K` is interpreted as an associated constant, not a new binding
  |
  = note:   expected enum `Cow<'_, str>`
          found reference `&'static str`
help: try wrapping the pattern in `std::borrow::Cow::Borrowed`
  |
6 |         std::borrow::Cow::Borrowed(Owner::K) => {}
  |         +++++++++++++++++++++++++++        +
help: introduce a new binding instead
  |
6 -         Owner::K => {}
6 +         Owner::other_k => {}
  |

1. rustc states that path pattern Owner::K is not interpreted as a binding pattern which is correct but nobody assumed that it was, a multi-segment path is never a pattern binding. Mentioning it is irrelevant, misleading & confusing.
2. Then, it suggests turning Owner::K into Owner::other_k which is basically always incorrect & never what the user intended.