diff options
| author | Stuart Cook <Zalathar@users.noreply.github.com> | 2025-04-08 20:55:09 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-04-08 20:55:09 +1000 |
| commit | 056756c7c4db570f93f8586828648fe02480dcb4 (patch) | |
| tree | 296476047e75fc891e2173ed9d278e81ca7da0b8 /compiler/rustc_codegen_llvm/src | |
| parent | ab80f575c485eccd57a86a92a7aabad5815270d7 (diff) | |
| parent | 45afefa7c025f3847439822b053edf76ae62e561 (diff) | |
| download | rust-056756c7c4db570f93f8586828648fe02480dcb4.tar.gz rust-056756c7c4db570f93f8586828648fe02480dcb4.zip | |
Rollup merge of #139421 - compiler-errors:upcast-no-principal-with-proj, r=oli-obk
Fix trait upcasting to dyn type with no principal when there are projections #126660 (which I had originally authored, lol) had a subtle bug that is the moral equivalent of #114036, which is that when upcasting from `dyn Principal<Projection = Ty> + AutoTrait` to `dyn AutoTrait`, we were dropping the trait ref for `Principal` but not its projections (if there were any). With debug assertions enabled, this triggers the assertion I luckily added in a2a0cfe82563146325674b8d437f9f9f6e703703, but even without debug assertions this is a logical bug since we had a dyn type with just a projection bound but no principal, so it caused a type mismatch. This does not need an FCP because this should've been covered by the FCP in #126660, but we just weren't testing a case when casting from a `dyn` type with projections 😸 Fixes #139418 r? ````@oli-obk```` (or anyone)
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions