-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Sema: Simplify BindingSet construction #86031
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
Open
slavapestov
wants to merge
10
commits into
swiftlang:main
Choose a base branch
from
slavapestov:binding-set-constructor-speedup
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+274
−162
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
01ca519
Sema: Sink Protocols down from BindingSet into PotentialBindings
slavapestov 6384c27
Sema: BindingSet::Defaults can just be a vector and not a map
slavapestov 36c7263
Sema: Factor out isDirectRequirement() from two places that check this
slavapestov 88d04b5
Sema: Extract coalesceIntegerAndFloatLiteralRequirements() from Bindi…
slavapestov 6c1593a
Sema: Stash the ProtocolDecl inside the LiteralRequirement
slavapestov 74fa1e7
Sema: BindingSet::Literals can just be a vector and not a map
slavapestov 88f347a
Sema: Collect defaults in PotentialBindings::infer()
slavapestov 77ee3da
Sema: Collect LiteralRequirements in PotentialBindings::infer()
slavapestov d795c18
Sema: Remove BindingSet::getConstraintSystem()
slavapestov 9a68d4a
Sema: De-duplicate defaults in inferTransitiveSupertypeBindings()
slavapestov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
Does this not make things slower when there duplicate defaultable constraints?
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.
That's a good point, do you mean the same constraint getting added multiple times, or multiple constraints with the same second type? I'll check for both and see if it can happen
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.
It could be both I think, this is the worst case when multiple type variables form an equivalence class and each has a literal requirement.
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.
I added an assertion to addDefault() to check for the same constraint being added twice. It doesn't trigger when building the stdlib or validation tests, but building swift-build trips it. I'll try to reduce a test case.
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.
Heh:
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.
We are merging as aggressively anymore since the hacks are disabled, i.e. all type variables in
1 + 2 + 3 + …used to be equated byoptimizeConstraints.