feat(Data): add payload slice accessor payload
#15
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.
My use case is to parse rather large register block from modbus powermeter.
I do it by designing exactly matching struct, deriving
zerocopy::FromBytes
for it, and the just creating it from register payload bytes as received from the powermeter. Sincezerocopy
crate has support for endianness, it looks to me like nearly perfect way to parse structured data represented in flat modbus registers.I see no reason to hide register payload from library user - let him exploit them :-)
Thanks.