-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Runtime] Add entry point to compare type context descriptors. #32476
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 type context descriptors. #32476
Conversation
@swift-ci please test |
Build failed |
@swift-ci please clean test os x platform |
81739f6
to
3c4e7bf
Compare
@swift-ci please test |
Build failed |
Build failed |
@swift-ci please clean test os x platform |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! It might also be helpful to have a comment on the swift_compareTypeContextDescriptors
declaration indicating the availability of the entry point.
The new function `swift_compareTypeContextDescriptors` is equivalent to a call through to swift::equalContexts. The implementation it the same as that of swift::equalContexts with the following removals: - Handling of context descriptors of kind other outside of ContextDescriptorKind::Type_First...ContextDescriptorKind::Type_Last. Because the arguments are both TypeContextDescriptors, the kinds are known to fall within that range. - Casting to TypeContextDescriptor. The arguments are already of that type. For now, the new function has "future" availability.
3c4e7bf
to
2c6d7d7
Compare
@swift-ci please smoke test and merge |
1 similar comment
@swift-ci please smoke test and merge |
The new function
swift_compareTypeContextDescriptors
is equivalent to a call through toswift::equalContexts
. The implementation it the same as that ofswift::equalContexts
with the following removals:ContextDescriptorKind::Type_First...ContextDescriptorKind::Type_Last
. Because the arguments are bothTypeContextDescriptors
, the kinds are known to fall within that range.TypeContextDescriptor
. The arguments are already of that type.For now, the new function has "future" availability.