Support python custom message builder and make Data field's type return MemoryView #380
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.
This PR is for resolving the following issue:
issue
Created
_PyCustomMessageBuilder
extendsMessageBuilder
, enabling the ability to customise theSegmentAllocate
method in Python. This allows allocation and data population within shared memory, and supports zero-copy inter-process data transfer by passing segment offsets.Fields of type
Data
now support being set with amemoryview
. When retrieving aData
field from aDynamicStructBuilder
, it will return a writablememoryview
, allowing users to modify the data directly. This enables memory to be pre-allocated and content to be modified in later, eliminating an extra copy. When retrieving aData
field from aDynamicStructReader
, it will return a read-onlymemoryview
, allowing user to read data without memory copy.