-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Constraint graph] Having "gathering all mentions" mean "gathering more mentions" #26718
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
DougGregor
wants to merge
4
commits into
swiftlang:master
from
DougGregor:constraint-graph-most-mentions
Closed
[Constraint graph] Having "gathering all mentions" mean "gathering more mentions" #26718
DougGregor
wants to merge
4
commits into
swiftlang:master
from
DougGregor:constraint-graph-most-mentions
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
…tions. When requesting all constraints that mention the given type variable, use a depth-first search to ensure that we find all mentions, rather than some subset of them. Fixes rdar://problem/54322807.
…raints Most clients of gatherConstraints() only care about the constraints directly on the given type variable or other type variables equivalent to it, while some also want to see constraints on fixed bindings as well. Split "gathering kind" further so we do less work to retrieve the constraints within an equivalence class for clients that only need that information.
Most of the logic is identical to that of AllMentions, except that we don't look through fixed bindings or traverse constraints.
…onstraints. Mimic the Swift <= 5.1 behavior of visiting only a single level of fixed bindings when gathering constraints, which should limit the amount of reprocessing of constraints.
@swift-ci please smoke test |
@swift-ci please test source compatibility |
@swift-ci please test compiler performance |
This approach is a dead-end; better to focus on getting the right answer with appropriate performance via #26691 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 requesting all constraints that mention the given type variable,
use a depth-first search to ensure that we find more mentions, rather
than some subset of them. This is meant to strike a balance that
fixes rdar://problem/54322807 while not greatly expanding the set
of constraints that are repeatedly visited.