Fix boxing empty blittable arrays #1158
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For blittable arrays, we make use of ReadOnlySpan to create the array. But when the array is empty, it seems we can get back the same array each time we call it. This causes issues when different instances of empty arrays are boxed in WinRT and we try to create an RCW for them because RCW creation expects it to be a new object. Addressing this by handling the empty array case to return a new empty array.
Also added tests which demonstrate this doesn't impact the non blittable array scenarios which don't make use of ReadOnlySpan.
Fixes #1146