cd0adc9d7b
Improve diagnostics for usage of qualified paths within tuple struct exprs/pats For patterns the old diagnostic was just incorrect, but I also added machine applicable suggestions. For context, this special cases errors for `<T as Trait>::Assoc(..)` patterns and expressions (latter is just a call). Tuple struct patterns and expressions both live in the value namespace, so they are not forwarded through associated *types*. r? ``@jdonszelmann`` cc ``@petrochenkov`` in https://github.com/rust-lang/rust/pull/80080#issuecomment-800630582 you were wondering why it doesn't work for types, that's why — tuple patterns are resolved in the value namespace. |
||
|---|---|---|
| .. | ||
| bad-builder.rs | ||
| bad-builder.stderr | ||
| ufcs-explicit-self-bad.rs | ||
| ufcs-explicit-self-bad.stderr | ||
| ufcs-partially-resolved.rs | ||
| ufcs-partially-resolved.stderr | ||
| ufcs-polymorphic-paths.rs | ||
| ufcs-qpath-missing-params.rs | ||
| ufcs-qpath-missing-params.stderr | ||
| ufcs-qpath-self-mismatch.rs | ||
| ufcs-qpath-self-mismatch.stderr | ||