-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Type checker] Move TypeChecker::resolveType() into TypeResolution. #18868
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 7 commits into
swiftlang:master
from
DougGregor:type-resolution-without-tc
Aug 21, 2018
Merged
[Type checker] Move TypeChecker::resolveType() into TypeResolution. #18868
DougGregor
merged 7 commits into
swiftlang:master
from
DougGregor:type-resolution-without-tc
Aug 21, 2018
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
…ypeResolver Do the easy part of separating the TypeResolver, which is chiefly responsible for turning TypeReprs into Types, from the TypeChecker.
…hecker. They’re still static methods for convenience, but they don’t depend on the type checker’s state.
…nce. Use the usual bag of tricks to eliminating dependence on the TypeChecker instance: static functions, LazyResolver callbacks, and emitting diagnostics on decls/ASTContext.
Now that type resolution is (almost completely) separated from the type checker instance, move resolveType() out to TypeResolution where it belongs.
@swift-ci please smoke test |
@swift-ci please smoke test |
@swift-ci please smoke test compiler performance |
@swift-ci please smoke test |
@swift-ci please smoke test compiler performance |
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.
Separate type resolution almost completely from the
TypeChecker
instance, and move the primary entry point (TypeChecker::resolveType()
) intoTypeResolution
.