diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2025-06-01 19:35:41 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-01 19:35:41 +0200 |
| commit | cd0adc9d7b2a2c7a41df53d6a384a42fbe2fce21 (patch) | |
| tree | f8e92415689f450bc2c424f4762d92fac102c267 /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | 9b0268a43b0a5b58f50c96ded25364037c019a61 (diff) | |
| parent | 8f765fc7a15b6a2f1de93251b9f65c6156fbfe33 (diff) | |
| download | rust-cd0adc9d7b2a2c7a41df53d6a384a42fbe2fce21.tar.gz rust-cd0adc9d7b2a2c7a41df53d6a384a42fbe2fce21.zip | |
Rollup merge of #140370 - WaffleLapkin:unqualified, r=jdonszelmann
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.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions