You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're currently polyfilling Set for everyone, really only to support distinct. I'd like in the spirit of #2407, I'd liek to propose removing the Set polyfill entirely, placing the onus on developers targeting IE10 and lower to provide their own polyfill.
Pros
Smaller library size
Less to maintain
I suspect the native Set impls may have better performance
All "modern" browsers support Set, it seems
Cons
Definitely a breaking change
I'm unsure if there are any quirks to this functionality between browser versions in the wild.
Might hurt more esoteric JS runtime targets (ala SmartTVs at Netflix?)
The text was updated successfully, but these errors were encountered:
We're currently polyfilling
Set
for everyone, really only to supportdistinct
. I'd like in the spirit of #2407, I'd liek to propose removing theSet
polyfill entirely, placing the onus on developers targeting IE10 and lower to provide their own polyfill.Pros
Cons
The text was updated successfully, but these errors were encountered: