Forward ObjC messages to _BridgedURL in rare compatibility cases #1301
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.
Some C APIs take in a
const void *that is expected to be aCFURLRef *in certain cases. When a Swift API is generated for these functions, they instead take anUnsafeRawPointer.Code passing an implicit raw pointer to a
struct URLusing&varnotation can cause issues if the C function assumes the address of aURLpoints to aNSURL *orCFURLRef. This used to work because anNSURLwas the first member ofstruct URL, but now that memory location contains the_SwiftURLclass.This PR allows us to restore the old behavior in very rare cases on Darwin where it's needed for compatibility by making
_BridgedURLanNSObjectand forwarding the ObjC messages it receives to the wrappedNSURL.