rdar://127199021, fix compatibility with apps that accidentally do [[[aSwiftArray class] new] mutableCopy] #73755
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.
Explanation: At least one app is managing to call +new on our private NSArray subclass, which doesn't work. This change makes it return a regular NSArray to maintain compatibility
Original PR: #73728
Reviewed by: @parkera
Risk: Low. This method is never supposed to be called, and cannot be called from Swift code, so normal usage will never execute it. It also never worked in the past, so the set of potentially impacted applications is "ObjC apps that are doing very unusual things with certain objects that used to be ObjC but are now Swift under the hood"
Resolves: rdar://127199021
Tests: Adds a test