[cxx-interop] Avoid spurious references to _OBJC_CLASS
symbols for C++ foreign reference types
#84665
+15
−0
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.
This removes erroneous references to
_OBJC_CLASS_$__xyz
symbols that Swift was emitting for certain usages of C/C++ foreign reference types. This was discovered when trying to iterate over a Swift array of foreign reference types using a Swift for-in loop.Builtin.canBeClass
was returning true for foreign reference types, which led to the optimizer specializing the genericcanBeClass<T>
function to unconditionally return true for foreign reference types. This meant that_isClassOrObjCExistential
for a foreign reference type evaluated to true, which made the Swift stdlib take the code path that was intended for Objective-C classes inArrayBuffer.getElement
, which assumed that theElement
type conforms toAnyObject
. Foreign reference types do not actually conform toAnyObject
.rdar://161814644