-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Runtime] Add entry point to compare conformance descriptors. #32471
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
[Runtime] Add entry point to compare conformance descriptors. #32471
Conversation
@swift-ci please test |
cfb4db2
to
dc67a84
Compare
@swift-ci please test |
Build failed |
Build failed |
dc67a84
to
2cc7c55
Compare
@swift-ci please test |
Build failed |
Build failed |
2cc7c55
to
ed23370
Compare
@swift-ci please test |
Build failed |
Build failed |
@swift-ci please clean test os x platform |
Build failed |
@swift-ci please clean test os x platform |
ed23370
to
575facd
Compare
@swift-ci please smoke test and merge |
575facd
to
be56d6f
Compare
The new function swift_compareProtocolConformanceDescriptors calls through to the preexisting code in MetadataCacheKey which has been extracted out from MetadataCacheKey::compareWitnessTables into a new public static function MetadataCacheKey::compareProtocolConformanceDescriptors. The new function's availability is "future" for now.
be56d6f
to
6d0c34c
Compare
@swift-ci please smoke test and merge |
1 similar comment
@swift-ci please smoke test and merge |
The new function
swift_compareProtocolConformanceDescriptors
just calls through to the preexisting code inMetadataCacheKey
which has been extracted out fromMetadataCacheKey::compareWitnessTables
into a new public static functionMetadataCacheKey::compareProtocolConformanceDescriptors
.The new function's availability is Swift Future for now.