Allow encode_into arbitrary buffers. - #1160
Open
zdxerr wants to merge 5 commits into
Open
Conversation
This file contains hidden or 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.
Lets
Encoder.encode_into()(bothmsgspec.msgpackandmsgspec.json) accept any writable, contiguous buffer-protocol object (e.g. amemoryviewontomultiprocessing.shared_memory.SharedMemory), not justbytearray.Currently the encode_into only works on bytearrays, this makes it impossible to use Python's SharedMemory with a zero-copy serialization.
fails with
This changes allows for arbitrary buffers that do not support resizing.
encode_into also return the number of newly written bytes. So offset + newly_written_bytes can by used as the offset for the next element when streaming data.