Add efficient event parsing. #1264
Draft
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.
Currently, decoding events uses
aeson. This works by converting the entire JS object structure intoValue. This incurs significant allocation overhead. Events are high frequency and minimizing allocations is important.This PR introduces an
Eventparser (Parser a) that bypasses the conversion intoValueby performing parsing inJSMdirectly on the rawJSVal(FFI.Eventobject).This works by replacing the
FromJSONconstraint in favor of the more efficientFromJSValand parsing in anExceptT, with two error cases.We expose a
FromJSON-like interface for end users. The code stays the same, butwithObject,(.:)SyntheticEventnomenclature.executeDecoderhelperFromJSValinstances.This opens up the door for more aeson-combinators like(.:?),(.!=), etc..:?,.!=added