perf(core): improve support for large collections #3573
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.
Previously
Collection.add/removewere defined with a spread parameter, which could result in perf degradation in very large collections. This change makes the first parameter accept also an array of items, skipping unnecessary copying of arrays when hydarting the collection.This is slightly breaking on type level, as it is no longer possible to do
coll.add(...items)with a generic array - it only works with a tuple. The solution is to docoll.add(items)instead, which will type check and is also more performant (no array copies).Closes #3572