-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Constraint graph] Restrict connected components to requested type variables #26369
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
Merged
DougGregor
merged 3 commits into
swiftlang:master
from
DougGregor:constraint-graph-connected-components-subgraph
Jul 27, 2019
Merged
[Constraint graph] Restrict connected components to requested type variables #26369
DougGregor
merged 3 commits into
swiftlang:master
from
DougGregor:constraint-graph-connected-components-subgraph
Jul 27, 2019
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
…riables. The API of the connected-components algorithm asks clients to provide the set of type variables of interest. However, the connected components algorithm itself was operating across the entire set of type variables, then narrowing the result down to the type variables of interest. Instead, only perform connected components on those type variables of interest, so that we are only doing work proportional to the subgraph we're working in.
@swift-ci please smoke test |
@swift-ci please test compiler performance |
In local testing, this took |
Well, that was unexpected. Looks like more debugging to do. |
Address a silly mistake that meant we were miscomputing connected components.
…iables. Simplify the connected-components computation slightly and make sure that it never performs work outside of the subgraph described by the input set of type variables.
@swift-ci please smoke test |
@swift-ci please test compiler performance |
1 similar comment
@swift-ci please test compiler performance |
@swift-ci please smoke test |
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.
The API of the connected-components algorithm asks clients to
provide the set of type variables of interest. However, the connected
components algorithm itself was operating across the entire set of
type variables, then narrowing the result down to the type variables
of interest. Instead, only perform connected components on those type
variables of interest, so that we are only doing work proportional to
the subgraph we're working in.