Avoid recursion when collecting prefix tree node values #3401
+17
−16
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.
Motivation
I noticed we were using recursion to accumulate all of the values in a prefix tree node and its children. Recursion can be quite slow, so I took a stab at removing it with a queue mechanism.
Implementation
The idea is to accumulate nodes in the queue and then pop one by one, adding to the result when appropriate.
On my benchmarks with a small sized tree, this approach is 2x faster than using recursion.
Note: we now push the values into the result in a slightly different order. I updated the tests to match. Notice that this makes no difference for our usages for completion since the editor is expected to sort the entries based on the
sortText
property.