-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[metadata prespecialization] Support classes with non-generic ancestors. #32174
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
[metadata prespecialization] Support classes with non-generic ancestors. #32174
Conversation
@swift-ci please test |
Build failed |
Build failed |
1698f86
to
52bf272
Compare
@swift-ci please test |
Build failed |
Build failed |
@swift-ci please test macos |
Build failed |
c70b256
to
b024fb7
Compare
@swift-ci please test macos |
Build failed |
b024fb7
to
c373a49
Compare
@swift-ci please test |
Build failed |
Build failed |
@swift-ci please test windows |
1 similar comment
@swift-ci please test windows |
c373a49
to
602faa2
Compare
@swift-ci please test |
Build failed |
Build failed |
@swift-ci please test windows |
@swift-ci please test |
Previously, metadata prespecialization for classes only occurred when all of a specialized generic class's ancestors were themselves generic. Here, that requirement is lifted so that generic classes with concrete ancestors are also eligible for prespecialization.
602faa2
to
8ec75d4
Compare
@swift-ci please test |
@swift-ci please test windows |
Build failed |
Build failed |
@swift-ci please test macos |
Build failed |
@swift-ci please clean test os x platform |
Build failed |
@swift-ci please clean test os x platform |
Previously, metadata prespecialization for classes only occurred when all of a specialized generic class's ancestors were themselves generic. Here, that requirement is lifted so that generic classes with concrete ancestors are also eligible for prespecialization.