Repository navigation
[DEV] New byteorder type - #66
Merged
Merged
Conversation
- fix benchmark example
MatrixEditor
marked this pull request as draft
August 1, 2026 08:14
- normalized byteorder resolution
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
1 participant
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.
Inheritbyte order (@struct(order=Inherit), also supported on@bitfield):a struct declared this way resolves its byte order from whichever struct embeds it (any nesting depth, including arrays), instead of a fixed order.
context.parentnow correctly resolvesdefault_struct_orderparameter to change the default struct order wheneverorder=Nonehas been set.Falls back to the regular default when used standalone. Also adds
ByteOrder + Struct(e.g.LittleEndian + Inner) to override the order at a single embedding site. Purely opt-in: structs that don't useInheritare unaffected.