Skip to content

swift-module-digester: always canonicalize super class types. #19590

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 8 commits into from
Sep 28, 2018

Conversation

nkcsgexi
Copy link
Contributor

No description provided.

@nkcsgexi
Copy link
Contributor Author

@swift-ci please smoke test

@slavapestov
Copy link
Contributor

Do you canonicalize all types, or just superclasses?

@nkcsgexi
Copy link
Contributor Author

We canonicalize all types when checking ABI stability. This patch is to canonicalize super class type names disregarding of checking ABI or source compatibility.

@nkcsgexi
Copy link
Contributor Author

@swift-ci please smoke test

@slavapestov
Copy link
Contributor

@nkcsgexi Why do you need to canonicalize superclass types but not other types when checking API stability?

@nkcsgexi
Copy link
Contributor Author

Because synthesizing type alias of the same name with an old type is an api-notes' way to maintain source-compatibility for many frameworks.

@slavapestov
Copy link
Contributor

@nkcsgexi I see, so its specific to imported modules? Maybe you should conditionalize the check on that hten.

@nkcsgexi
Copy link
Contributor Author

yeah, i think it's specific to imported module. Since we'll deploy ABI checker for Swift modules with all types canonicalized, i'm not sure it's useful to introduce another flag.

@nkcsgexi
Copy link
Contributor Author

@swift-ci please smoke test

@nkcsgexi nkcsgexi merged commit 64ef8ec into swiftlang:master Sep 28, 2018
@nkcsgexi nkcsgexi deleted the canonical-super-classtype branch September 28, 2018 02:00
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.

2 participants