Obj-C class metatypes should never satisfy Obj-C existentials #69435
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Given this
the casts
C.self is any P
andC.self as? any P
should always fail, because the metatype ofC.self
does not have anf()
implementation.These casts previously succeeded because the runtime implementation deferred to Obj-C's
[o conformsToProtocol:p]
, and that behaves differently depending on whethero
is a class instance or a Class itself.Since these casts should never succeed, I've just modified the Swift runtime logic to fail whenever the source of the cast is an Obj-C Class and the target is a protocol existential.
Resolves: rdar://106973771