Uh oh!
There was an error while loading. Please reload this page.
check for inference var leaks before rollback - #100745
Conversation
lcnr
commented
Aug 19, 2022
xd, should change my |
rust-log-analyzer
commented
Aug 19, 2022
The job Click to see the possible cause of the failure (guessed by this bot) |
compiler-errors
commented
Aug 19, 2022
Hehe what a coincidence that I get assigned this PR. I actually tried this with very similar motivation, but hit the same debug assertions as you're hitting and gave up. Curious to see if we can get this totally solved, though. |
bors
commented
Aug 31, 2022
☔ The latest upstream changes (presumably #101225) made this pull request unmergeable. Please resolve the merge conflicts. |
lcnr
commented
Sep 8, 2022
so afaict inference variables actually remain valid, we just drop any unifications from inside of the snapshot 🤔 so i guess while still weird, this isn't a soundness issue? idk, still unhappy but don't know of an easy way to improve anything here |
When rolling back a snapshot, we must be careful to not leak any inference vars created in that snapshot. This PR implements an even stronger check by not allowing any inference vars during rollback.
Inspired by #100473 (comment), I think this is worth the additional, otherwise pretty useless,
TypeVisitableimpls.r? @rust-lang/types