-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[CS] Use a MapVector to cache resolved overloads #28593
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
Merged
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
@swift-ci please test |
@swift-ci please test source compatibility |
@swift-ci please smoke test compiler performance |
xedin
approved these changes
Dec 5, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! I have left one meta comment inline and I'm very excited to see ResolvedOverloadSetListItem
go away!
Rather than maintaining a linked list of overload choices, which must be linearly searched each time we need to lookup an overload at a given callee locator, use a MapVector which can be rolled back at the end of a scope. Remove ResolvedOverloadSetListItem in favor of using SelectedOverload, which avoids the need to convert between them when moving from ConstraintSystem to Solution.
With the new way of caching overloads in the constraint system, we no longer allow different overloads to be resolved for the same locator in the same scope. Adjust the property wrapper logic so that it appends Member locator elements for nested lookups.
3f8c3fa
to
40750c0
Compare
@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.
Rather than maintaining a linked list of overload choices, which must be linearly searched each time we need to lookup an overload at a given callee locator, use a
MapVector
which can be rolled back at the end of a scope.Remove
ResolvedOverloadSetListItem
in favor of usingSelectedOverload
, which avoids the need to convert between them when moving fromConstraintSystem
toSolution
.