Iterative approach for parsing queries #4
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.
That's an experimental attempt to replace current recursive algorithm with the iterative approach.
Currently only the parsing part is implemented and the functionality is exported as
parse_raw_iterfunction. I've copied tests from raw_parse and fixed them with some help of LLMs.I've added the
parse_raw_iterto the test with benchmark insidetests/raw_parse_test.rsand the results are following:with
--releaseflag on my machine:So, it's slightly slower than current recursive approach. I've tried different ideas to optimize my code but have managed to make it fully on-par yet.