Upgrade to nom 8.0.0 #4105
Merged
Upgrade to nom 8.0.0 #4105
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
in nom 8, `many0` doesn't accumulate when used within `recognize`
Member
|
That was a lovely surprise - thank you very much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
See https://web.archive.org/web/20250128194312/https://unhandledexpression.com/nom-8/
The main improvement with nom 8 is that it now recognises when a parser's output isn't used, and potentially avoids allocation in those cases, which lets us remove the hack introduced in #3886, along with catching a few other missed cases