Skip to content

[Conformance checking] More refactoring of associated type inference. #13378

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

Conversation

DougGregor
Copy link
Member

Move the rest of associated type inference into the new source file,
and split RequirementEnvironment into its own AST-level header, because it
can be re-used and has no ties to the type checker.

Move the rest of associated type inference into the new source file,
and split RequirementEnvironment into its own AST-level header, because it
can be re-used and has no ties to the type checker.
@DougGregor
Copy link
Member Author

@swift-ci please smoke test and merge

@@ -0,0 +1,124 @@
//===--- RequirementEnvironment.h - Swift Language Type ASTs ----*- C++ -*-===//
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wrong description here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Drat, okay. Thanks!

@@ -0,0 +1,231 @@
//===--- RequirementEnvironment.cpp - ASTContext Implementation -----------===//
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also wrong description here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(FWIW, I fixed these in a subsequent, completely-unrelated PR)

@swift-ci swift-ci merged commit 6fb2ad1 into swiftlang:master Dec 12, 2017
@DougGregor DougGregor deleted the associated-type-infer-refactor-more branch December 14, 2017 18:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants