[Constraint] Conditionally increase member lookup impact #87038
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When member lookup constraint simplification has succeeded on a type or subtype, increase the impact for failures on super types as the success is the more likely path. Includes implementation to record the success of the member lookup
Contributor
Author
|
Need to add test from rdar::169736579 and make some of the new members of ConstraintSystem private. Code from rdar no longer finds a spurious member lookup |
Contributor
Author
|
@swift-ci please test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When member lookup constraint simplification has succeeded on a type or subtype, increase the impact for failures on super types as the success is the more likely path.
Includes implementation to record the success of the member lookup