diff options
| author | León Orell Valerian Liehr <me@fmease.dev> | 2024-02-18 05:10:18 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-18 05:10:18 +0100 |
| commit | 9811358f596b8f5b3a3dff89a7b74386715fd902 (patch) | |
| tree | 11624b2550ca2b41877de88cf4f48a1bdb06dae2 /compiler/rustc_parse/src/errors.rs | |
| parent | 8ba0ad0775ff048d834954343c856545e239c373 (diff) | |
| parent | 38a2a65f0b7bcf137bc4756c4fa1db1c3ba3b0c9 (diff) | |
| download | rust-9811358f596b8f5b3a3dff89a7b74386715fd902.tar.gz rust-9811358f596b8f5b3a3dff89a7b74386715fd902.zip | |
Rollup merge of #121221 - fmease:refactor-astconv-assoc-item-bindings, r=compiler-errors
AstConv: Refactor lowering of associated item bindings a bit
Split off from #119385 as discussed, namely the first two commits (modulo one `FIXME` getting turned into a `NOTE`).
The second commit removes `astconv::ConvertedBinding{,Kind}` in favor of `hir::TypeBinding{,Kind}`. The former was a — in my opinion — super useless intermediary. As you can tell from the diff, its removal shaves off some code. Furthermore, yeeting it will make it easier to implement the type resolution fixes in #119385.
Nothing in this PR should have any semantic effect.
r? `@compiler-errors`
<sub>**Addendum** as in #118668: What I call “associated item bindings” are commonly referred to as “type bindings” for historical reasons. Nowadays, “type bindings” include assoc type bindings, assoc const bindings and RTN (return type notation) which is why I prefer not to use this outdated term.</sub>
Diffstat (limited to 'compiler/rustc_parse/src/errors.rs')
0 files changed, 0 insertions, 0 deletions