Allow aliasing between read-only buffers #12204
Merged
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.
Motivation:
Aliasing is only a problem when mutation is involved.
Since making a buffer read-only is irreversible, we can permit them to share the underlying memory.
Modification:
Add a
Buffer.copy
method that takes an argument for whether the resulting buffer should be read-only or not.If both original and copy buffers are read-only, then reuse the existing structural sharing mechanics of the const buffers, to make both read-only buffers share the same underlying memory.
Result:
Copying read-only buffers can now offer a useful optimisation.