Add option to reverse aggregate fields #34
Draft
Conversation
This file contains 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.
The intended use case for this feature is serializing data structures to a binary format compatible with SystemVerilog struct. In SystemVerilog, the last field in the struct is actually at the lowest address and the first field is in the highest address. By adding an option to reverse field serialization order, it's possible to interchange binary data with SystemVerilog when all struct members have the same byte alignment.
I did not add reorder to any aggregate type_info functions. As they are used now, I don't think it will change any functionality. Users of reverse_aggregate_fields would have to understand the binary compatibility issues
Please excuse the whitespace trimming in README.md.
Draft until tests added.