diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2022-07-18 08:39:59 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-07-18 08:39:59 +0900 |
| commit | 3c2175b8a2452e80a3eb8a8d9f6f9cb312908550 (patch) | |
| tree | cd7c66e44a6d82985e24ad64512ea7fda8947200 /compiler/rustc_mir_transform/src/coverage/debug.rs | |
| parent | cc35c787aa67e325901ca3af74699dc7727b764d (diff) | |
| parent | 23cb89ea3810bf63a70b9e7b473c046457982179 (diff) | |
| download | rust-3c2175b8a2452e80a3eb8a8d9f6f9cb312908550.tar.gz rust-3c2175b8a2452e80a3eb8a8d9f6f9cb312908550.zip | |
Rollup merge of #99356 - compiler-errors:tait-in-assoc-ty-supertraits, r=oli-obk
Do not constraint TAITs when checking impl/trait item compatibility Check out the UI test for the example. Open to other approaches to fix this issue -- ideally we _would_ be able to collect this opaque type constraint in a way to use it in `find_opaque_ty_constraints`, so we can report a better mismatch error in the incompatible case, and just allow it in the compatible case. But that seems like a bigger refactor, so I wouldn't want to start it unless someone else thought it was a good idea. cc #99348 r? ``@oli-obk``
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/debug.rs')
0 files changed, 0 insertions, 0 deletions
