mirror of
https://github.com/rust-lang/rust.git
synced 2025-06-19 11:07:32 +00:00
3b780fc279
Check that RPITs constrained by a recursive call in a closure are compatible Fixes #99073 Adapts a similar visitor pattern to `find_opaque_ty_constraints` (that we use to check TAITs), but with some changes: 0. Only walk the "OnlyBody" children, instead of all items in the RPIT's defining scope 1. Only walk through the body's children if we found a constraining usage 2. Don't actually do any inference, just do a comparison and error if they're mismatched ---- r? `@oli-obk` -- you know all this impl-trait stuff best... is this the right approach? I can explain the underlying issue better if you'd like, in case that might reveal a better solution. Not sure if it's possible to gather up the closure's defining usages of the RPIT while borrowck'ing the outer function, that might be a better place to put this check... |
||
|---|---|---|
| .. | ||
| constraints | ||
| diagnostics | ||
| region_infer | ||
| type_check | ||
| borrow_set.rs | ||
| borrowck_errors.rs | ||
| constraint_generation.rs | ||
| consumers.rs | ||
| dataflow.rs | ||
| def_use.rs | ||
| facts.rs | ||
| invalidation.rs | ||
| lib.rs | ||
| location.rs | ||
| member_constraints.rs | ||
| nll.rs | ||
| path_utils.rs | ||
| place_ext.rs | ||
| places_conflict.rs | ||
| prefixes.rs | ||
| renumber.rs | ||
| session_diagnostics.rs | ||
| universal_regions.rs | ||
| used_muts.rs | ||