diff options
| author | bors <bors@rust-lang.org> | 2025-09-12 14:28:42 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2025-09-12 14:28:42 +0000 |
| commit | a171994070dc18c3a32fc1aa2d98cf03ae96b63e (patch) | |
| tree | f154c23ea33b4eced0f770a6c7caeb965c6a5c08 /compiler/rustc_middle/src/query/erase.rs | |
| parent | 408eacfb95ea19e248c0fe5e377980bc00682c1b (diff) | |
| parent | cf224ea1fbe2fb7eb64812288338a2c4cfe1d084 (diff) | |
| download | rust-a171994070dc18c3a32fc1aa2d98cf03ae96b63e.tar.gz rust-a171994070dc18c3a32fc1aa2d98cf03ae96b63e.zip | |
Auto merge of #146329 - lcnr:opaque-type-infer-alias-candidates, r=BoxyUwU
consider item bounds for non-yet-defined opaque types Based on rust-lang/rust#140405. fixes https://github.com/rust-lang/trait-system-refactor-initiative/issues/182 fixes https://github.com/rust-lang/trait-system-refactor-initiative/issues/196 fixes https://github.com/rust-lang/trait-system-refactor-initiative/issues/205 there's some jank here, see https://github.com/rust-lang/trait-system-refactor-initiative/issues/229 ## Design If the self type is an inference variable which has been sub-unified with am opaque type, we need to incompletely guide inference to avoid breakage. In this case, we - look at the item bounds of all sub-unified opaque types, and - blanket impls which do not constrain the self type Even if there are applicable candidates, we always force their certainty to be `Maybe`, so they will always have to be reproven once we've constrained the inference variable. This is a bit iffy, see the added tests. r? `@BoxyUwU`
Diffstat (limited to 'compiler/rustc_middle/src/query/erase.rs')
0 files changed, 0 insertions, 0 deletions