currently the Infcx can store both old and new style constraints. This is kind of annoying from an implementation complexity POV. But also it means that it's easy to have logic written for old style region cosntraints which silently ignores new-style constraints which is wrong.
For example scrape_region_constraints in mir typeck seems to ignore abby's constraints I think? as well as helper methods like take_and_reset_region_constraints
We should only have one kind of region constraint and just use it everywhere even before abby is stable. This will need us to:
#t-types/trait-system-refactor > `unic-ucd-name-0.9.0` minimization @ 💬
#t-types/assumptions-on-binders > merging old and new style constraints
currently the Infcx can store both old and new style constraints. This is kind of annoying from an implementation complexity POV. But also it means that it's easy to have logic written for old style region cosntraints which silently ignores new-style constraints which is wrong.
For example
scrape_region_constraintsin mir typeck seems to ignore abby's constraints I think? as well as helper methods liketake_and_reset_region_constraintsWe should only have one kind of region constraint and just use it everywhere even before abby is stable. This will need us to:
VisibleForLeakCheck#30UndoLogto not be ass for perf :3#t-types/trait-system-refactor > `unic-ucd-name-0.9.0` minimization @ 💬
#t-types/assumptions-on-binders > merging old and new style constraints