remove Function.name polyfill

[davidchambers]

Function.name has been widely supported for years at this point, so the polyfill no longer seems necessary.

[Bradcomp]

I don't know how important IE compatibility is for you, but even IE 11 doesn't support Function.name. It looks like they are certainly moving away from IE support though https://techcommunity.microsoft.com/t5/microsoft-365-blog/microsoft-365-apps-say-farewell-to-internet-explorer-11-and/ba-p/1591666

[davidchambers]

Good point, Brad. My understanding is that there is no way for a user to ensure that typeRep.name evaluates as intended in browsers that do not support this language feature. This change is actually more breaking than adopting const and =>, as those language features can be transpiled to ES5.

Perhaps this pull request should wait a few years. What do others think?

[Avaq]

Perhaps this pull request should wait a few years. What do others think?

Since the name is central to the design of this lib, I guess it'd be good to keep the polyfill around until we're certain it's no longer needed.

[davidchambers]

Let's revisit this in a few years. :)