Data.mutableSpan and Data.mutableBytes do not perform uniqueness check #1530
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.
Unfortunately the
mutableSpan
andmutableBytes
accessors onData
do not currently perform a uniqueness check to trigger CoW. This means that you can mutate aData
via its mutable span even if it references a shared storage. This updates the implementation to trigger CoW for the shared storage representations when accessing the mutable spans as well as a unit test to ensure a copy occurs when not uniquely referenced (and that no copy occurs if the storage is uniquely referenced).