Repository navigation
Conversation
Introduce Parser.skipBits(length) for advancing the bit cursor during bit-field parsing without adding fields to the parsed result. Document the API in README and add regression tests.
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.
Adds
Parser.skipBits(length), which moves the bit cursor forward inside a bit-field sequence without adding anything to the parsed object. Today the workaround is to definebit1throughbit32fields and then throw the values away.lengthmust be a positive integer, and options such asassertare rejected.npm run format,npm run buildandnpm testpass (192 tests).Closes #91