Parser: Allow specifying custom depth for optimization#1
Open
provigz wants to merge 1 commit intolispparser:masterfrom
Open
Parser: Allow specifying custom depth for optimization#1provigz wants to merge 1 commit intolispparser:masterfrom
Parser: Allow specifying custom depth for optimization#1provigz wants to merge 1 commit intolispparser:masterfrom
Conversation
`int depth` can now be specified in `sexp::Parser::from_` functions. It can be used for omitting (not parsing) structures deeper than `depth` in the tree, starting from 0. This can optimize reading a few base properties from an otherwise big file. The omitted objects/arrays will not be present in the parsed `Value` tree.
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.
int depthcan now be specified insexp::Parser::from_*functions. It can be used for omitting (not parsing) structures deeper thandepthin the tree, starting from 0. This can optimize reading a few base properties from an otherwise big file.The omitted objects/arrays will not be present in the parsed
Valuetree.Additionally fixes an oversight where
sexp::Parser::from_string_*didn't passuse_arraystosexp::Parser::from_stream_*.