Fix handling multiple levels of nested blocks #12
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.
When parsing something like:
I noticed a strange issue:
What I actually expect there is sub3.
Changes:
When nesting > 0, if the next token is {, it means we've entered a new block.
So we move the cursor back and continue with the same logic as when nesting == 0 in old code.
Now NextBlock() correctly steps into the nested block and Val() returns the expected first item (sub3).