diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2022-01-13 08:11:19 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-01-13 08:11:19 +0100 |
| commit | b45a819bef7208192886584c6ef52654bcd26299 (patch) | |
| tree | ce8b66533b0743e8e3c28ec7826f51885bf90148 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | e045c79c2d8697ef7ab2e25c3165cb5896f163ba (diff) | |
| parent | bdeeb07bf6400622074f04ca2523dac1512ab662 (diff) | |
| download | rust-b45a819bef7208192886584c6ef52654bcd26299.tar.gz rust-b45a819bef7208192886584c6ef52654bcd26299.zip | |
Rollup merge of #92006 - oli-obk:welcome_opaque_types_into_the_fold, r=nikomatsakis
Welcome opaque types into the fold r? ```@nikomatsakis``` because idk who else to bug on the type_op changes The commits have explanations in them. The TLDR is that * 5c4600227329a273c0c6c844e4a10ce650ead601 stops the "recurse and replace" scheme that replaces opaque types with their canonical inference var by just doing that ahead of time * bdeeb07bf6400622074f04ca2523dac1512ab662 does not affect anything on master afaict, but since opaque types generate obligations when instantiated, and lazy TAIT instantiates opaque types *everywhere*, we need to properly handle obligations here instead of just hoping no problematic obligations ever come up.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions