json: refine whitespace rules to avoid runaways#7866
Merged
ochafik merged 1 commit intoggml-org:masterfrom Jun 11, 2024
Merged
Conversation
json: refine whitespace rules to avoid runaways
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.
Quick follow up to #7841 (@HanClinto I took the bait of your "good start" 🤪)
Defining whitespace as
ws ::= | " " | "\n" [ \t]{0,20}allows compact inline{"a": 1}, spacy inline{ "a" : 1 }and indented JSON, but disallows multiple empty lines, multiple spaces not in an indenting context, etc.For instance, this removes the trailing spaces generated by the following call:
Show output from master
Seems to perform similarly to master with the couple of attempts I've done.
Show benchmark commands
Note: also tested
ws ::= | " " | "\n" (" "{0,10} | "\t"{0,10})but it's slower, probably because of the extra stack / alternatives overhead.