Don't use array.push(...spread) with unknown input #7848
Merged
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.
Using
array.push(...spread)
is quite nice and convenient, but unfortunately providing too many arguments to a function call can cause a stack overflow, which happened to us.Minimum reproduction Twiddle
Also unfortunately, using
Array#concat
changes the API, since it returns a new array rather than modifying the original. Also also unfortunately, simply iterating over an array and pushing one-by-one is significantly slower than using spread or concat.Performance tests JSBin
This implementation is a hybrid approach of looping and spreading that remains stack safe.
If we can guarantee that using concat is safe, that'd be an even better implementation since it's both part of the standard lib and also faster.