AssociatedTypeInference: Make a cycle breaking hack more principled #82159
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.
We would return an ErrorType without diagnosing anything from NormalProtocolConformance::getTypeWitnessAndDecl() to signal a transient condition to associated type inference. But other callers that receive an ErrorType don't expect that this can happen, and they in turn won't diagnose anything. So we'd end up in SILGen with a broken AST.
Instead, push the cycle break up into getWitnessTypeForMatching(), and remove the hack from getTypeWitnessAndDecl(). If someone else calls getTypeWitnessAndDecl() and that causes a request cycle, we will now diagnose the request cycle via the usual mechanism.
Fixes rdar://120388028.