diff options
| author | bors <bors@rust-lang.org> | 2022-09-25 12:00:37 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-09-25 12:00:37 +0000 |
| commit | 4652f5eb25b76c24fc40b7267d87a07d5876901f (patch) | |
| tree | 0201d243a4e2fa272709a5183014de07ad5014e3 /compiler/rustc_interface/src/errors.rs | |
| parent | 6f6010b08bd5e5dd0d03d4abf35a3acc4d2433a2 (diff) | |
| parent | 102c61f11076d4cd71a117c358f4bdf93054d08e (diff) | |
| download | rust-4652f5eb25b76c24fc40b7267d87a07d5876901f.tar.gz rust-4652f5eb25b76c24fc40b7267d87a07d5876901f.zip | |
Auto merge of #100865 - compiler-errors:parent-substs-still, r=cjgillot
Don't drop parent substs when we have no generic parameters in `create_substs_for_ast_path` This bug is being shadowed by an explicit check for `generics.params.is_empty()` in the only parent caller that could trigger it (`create_substs_for_associated_item`). I triggered it on another branch where I'm messing around with astconv stuff. Also, the second commit simplifies `create_substs_for_associated_item`. Removing that explicit check I mentioned above^ and also the special case call to `Astconv::prohibit_generics` causes the UI test `src/test/ui/structs/struct-path-associated-type.stderr` to change, but I think that it's clearer now. The suggestion to remove the generics is actually useful.
Diffstat (limited to 'compiler/rustc_interface/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
