introduce hasKnownResult to optimize several parsers.#348
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## main #348 +/- ##
==========================================
+ Coverage 96.56% 96.91% +0.34%
==========================================
Files 9 9
Lines 1049 1103 +54
Branches 94 98 +4
==========================================
+ Hits 1013 1069 +56
+ Misses 36 34 -2
Continue to review full report at Codecov.
|
regadas
approved these changes
Jan 11, 2022
Contributor
regadas
left a comment
There was a problem hiding this comment.
It will be interesting to see new benchmark numbers.
Contributor
|
@johnynek could you rebase this? |
Contributor
Author
|
Yes! I will do. Thanks for the review. Note, this optimization will mostly apply to flatMap, and most parser don't need flatMap (e.g. our json benchmarks don't use flatMap). But still, I thought it was worth trying to limit the worst case. |
Contributor
Author
|
@regadas let me know if this looks good. |
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.
Often, we can statically see what the result value will be if a parser succeeds.
If we know this, can optimize map, select and flatMap.
In particular, we can avoid reallocating a parser inside each flatMap.
Most users should avoid using flatMap anyway, but in a library function, you might need flatMap but want to get the optimization when the user passes you a constant parser.