Avoid recursion when parsing documents #78
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.
Deeply nested documents can cause a stack overflow due to recursion. Avoid that by using a heap based stack instead.
This includes a first commit to infer the sibling index from the parent, so that the iterative approach is simpler
This would resolve issues #66 and (arguably) #68
Since there is no maximum depth option added here, it is possible to go fully OOM, but much larger documents are supported than previously.