Don't propagate the thisArg mistake

[domenic]

A paragraph (under "Asynchronous Values") is dedicated to adding the thisArg to promises, and throughout the rest of the document it is assumed you have a thisArg for other primitives and their transformation/consumption functions. I would rather argue that adding thisArg to arrays was a mistake from the time before Function.prototype.bind and especially before arrow functions, and ignore it in all discussions of future technology

[kriskowal]

I think there is still a good argument for closure avoidance since we pay for it in garbage collection.