-
Notifications
You must be signed in to change notification settings - Fork 10.5k
GSB: Rewrite getConformanceAccessPath(), again #37296
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
slavapestov
merged 1 commit into
swiftlang:main
from
slavapestov:cleaner-conformance-access-path
May 7, 2021
Merged
GSB: Rewrite getConformanceAccessPath(), again #37296
slavapestov
merged 1 commit into
swiftlang:main
from
slavapestov:cleaner-conformance-access-path
May 7, 2021
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
The new approach is to not look at RequirementSources at all. Instead, we exhaustively enumerate all conformance access paths, beginning from the root conformance requirements in the signature, then doing all conformance requirements from those protocols' requirement signatures, and so on. We enumerate conformance access paths in breadth first order by length until we find the one we want. The results are memoized. This fixes a regression with another change I'm working on. The test case does not fail with this PR alone, but I'm adding it now anyway.
@swift-ci Please smoke test |
@swift-ci Please test source compatibility |
@swift-ci Please test compiler performance |
The comparison report is bogus again for 'Release', but I checked the stats-dir output manually and confirmed we spend ~100ms total in the new 'get-conformance-access-path' FrontendStatsTimer. |
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 new approach is to not look at RequirementSources at all. Instead,
we exhaustively enumerate all conformance access paths, beginning
from the root conformance requirements in the signature, then doing
all conformance requirements from those protocols' requirement
signatures, and so on.
We enumerate conformance access paths in breadth first order by
length until we find the one we want. The results are memoized.
This fixes a regression with another change I'm working on. The
test case does not fail with this PR alone, but I'm adding it now
anyway.