Move FulfillmentContext out of InferCtxt #31588
Merged
+28
−30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
context: moving back to a layered approach to type checking.
It looks like they'd not ended up tightly coupled in the time one was owned by the other. Every instance outside of
FnCtxt.inh
was from anInferCtxt
created and dropped in the same function body.This conflicts slightly with #30652, but there too it looks like the
FulfillmentContext
is from anInferCtxt
that is created and dropped within the same function body (across one call to a module-private function).That said, I heard that the PR that originally moved
FulfillmentContext
intoInferCtxt
was big, which leaves me concerned that I'm missing something.r? @nikomatsakis