Polyfill symbols in set, map and array alike #1880
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes #1878, an omission in Set backport. Reuses existing utils. Should restore IE11 compatibility.
|
Thanks! Will release soon |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #1878, an omission in Set backport. Reuses existing utils. Should restore IE11 compatibility.
Added unit testsCan't, tests use modern Node which has an okay Symbol.Updated changelogNot creating a new version myself. Or should I write log anyway?or as separate PR on the). For new functionality, at least API.md should be updatedgh-pagesbranch. Please refer to this PRAdded typescript typingsRegression fix, no API change.npm run perfnpm run test:performance)