add integer parsing based off https://github.com/nodejs/llparse/pull/32 And Fix Pausing#8
Merged
add integer parsing based off https://github.com/nodejs/llparse/pull/32 And Fix Pausing#8
Conversation
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.
I'm going to add in integer parsing myself based off @arthurschreiber but with Indutny's requested features and nitpicks.
I will need to make a frame parser for http2 for the aiohttp developers soon since were looking into implementing http/2 protocols, however I would like something a little bit faster than python at parsing frames instead of what hyperframe does which is collecting 9 bits and then depacking. This will skip all of that and cut right to the juicy portions without bloating memory.
SEE: nodejs/llparse#32 for more details.
Here's a dummy example based off RFC 9113 section 4.1