This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
Fallback to old behavior when marshaling a non-blittable fixed buffer #20575
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.
After some offline discussions, we've decided to revert back to the old behavior when marshaling a non-blittable fixed buffer since all alternatives will very likely break someone and we don't get much real benefit out of it.
Also, add an assert for debug and checked builds to we can make sure that we don't try to marshal non-blittable fixed buffers while developing runtime features.
Supercedes #20558, #20263, and #20375