[3.0] Handle inaccurate ObjC nullability in id
-as-Any
bridging.
#4387
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.
Make
id
-as-Any
bridging resilient against ObjC APIs that claim to be_Nonnull
but produce nil in practice, by wrapping up nils asAnyObject?
s-inside-Any
s instead of as invalidAnyObject
s-inside-Any
s. rdar://problem/27874026