-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Add a runtime-internal function, _enumerateTypes(fromImageAt:conformingTo:_:)
, that will walk the protocol conformance tables looking for types that conform to a given protocol.
#40515
Conversation
839a6bd
to
a64dcfc
Compare
a64dcfc
to
14e6793
Compare
@swift-ci please test |
Build failed |
14e6793
to
ef1ac64
Compare
@swift-ci please test |
9fd12ee
to
6690e14
Compare
@swift-ci please test |
6690e14
to
0edccaa
Compare
@swift-ci please test |
Build failed |
Build failed |
Build failure appears unrelated to my changes, caused by swiftlang/swift-package-manager#3929. @tomerd |
0edccaa
to
ac06b0a
Compare
@swift-ci please test |
ac06b0a
to
65a039c
Compare
@swift-ci please test |
Build failed |
Build failed |
Build failed |
Build failed |
9b50342
to
a21eac6
Compare
Can we reuse the existing logic in the runtime, used by the conformance cache, that crawls the metadata in an image looking for matching conformances? |
a21eac6
to
7aa9f5b
Compare
@swift-ci please test |
That's effectively what this new function does (as much as is possible.) |
Build failed |
@swift-ci please test |
Build failed |
Build failed |
7aa9f5b
to
cb22ec5
Compare
@swift-ci please test |
I stripped out special handling for |
Build failed |
…ngTo:_:), that will walk the protocol conformance tables looking for types that conform to a given protocol.
cb22ec5
to
87232e5
Compare
@swift-ci please test |
Build failed |
Build failed |
Build failed |
Add a runtime-internal function,
_enumerateTypes(fromImageAt:conformingTo:_:)
, that will walk the protocol conformance tables looking for types that conform to a given protocol.Resolves rdar://67501458.