fix: Fix incorrect data size handling in struct layout Update mod.rs #372
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.
An issue with the struct layout where
Size
andData
were incorrectly assumed to have fixed sizes. Specifically,Size
was defined asu32
(4 bytes), followed byData
(incorrectly assumed to always be 4 bytes), and thenC
(CRC32, 4 bytes). This doesn't align with the actual requirements sinceData
can have a variable length. I've updated the implementation to correctly handleData
as a variable-length field, ensuring the struct layout matches the intended design. This should resolve any inconsistencies in memory alignment and data parsing.