Inline row decoder applicative for ~14% performance gains - #44
Merged
Conversation
mzabani
changed the title
mzabani
marked this pull request as ready for review
August 9, 2026 13:41
mzabani
force-pushed
the
inline-row-decoder-applicative
branch
from
August 9, 2026 13:42
f2fd19a to
e72747b
Compare
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
1 participant
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.
A ~14.3% performance improvement in the Tuple Stream benchmark. Looking at GHC Core output, now the CPS parser isn't allocating intermediary
Parser (a -> b)structures any longer, and it's finally behaving like I always expected it to: call a field decoder, take the response and pass it to the success continuation of the Parser; call then next field decoder, etc.Total memory allocation reduced by ~6%.