Repository navigation
Make ObjectHeader the header enum - #674
Merged
Merged
Conversation
After the READ qualifier work, ObjectHeader was a wrapper around a single HeaderDetails field, so every consumer reached through `.details` and the parser wrapped each header in ObjectHeader::new. The enum is now the header, with variation(), qualifier(), count() and format() on it.
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
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.
After #628 the crate-private
ObjectHeaderwas a one-field wrapper aroundHeaderDetails. It is now that enum itself, withvariation(),qualifier(),count()andformat()on it, removing 68.detailsaccesses and 7 wrapper constructions across the parser, master and outstation. Behavior-neutral (pinned by the header identity, read-header, master and outstation tests); the no-panic check passes.