🐛 Avoid recursion in generators due to no tail-call optimizations #739
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.
What is this?
The check within the
waitFor
util was originally created as a recursive function. With recent changes, the util was converted to make use of the cancelability of generators. However, generators cannot be tail-call optimized like the previous implementation was. This is due to technical reasons within V8 around the nature of how generator'snext()
function handles script evaluation.Because the
waitFor
util polls and may run for a long time, the lack of tail-call optimization caused the call stack to continuously grow the longer the util took to resolve. Eventually this could/will result in call stack errors (#735).This PR refactors the generator within the util to use a
while (true)
loop rather than a recursiveyield*
. The infinite loop is broken if thepredicate
passes at least once and at least one more time ifidle
is provided.