Array.prototype.sort( callbackfn [ , thisArg ] )

Jordan Harband ljharb at gmail.com
Tue Nov 12 07:27:07 UTC 2019


What's the issue with creating a new function for that case, that accesses
the other list in its closure?

(Arrow functions, or .bind, are cheap; the `thisArg` makes it basically
impossible to add extra args to all functions that have it, and is almost
never used)

On Mon, Nov 11, 2019 at 11:03 PM Michaël Rouges <michael.rouges at gmail.com>
wrote:

> For example, to easily sort the values, compared with another list, using
> only one iteration.
>
> Le mar. 12 nov. 2019 à 07:42, Jordan Harband <ljharb at gmail.com> a écrit :
>
>> I'd assume it's because sort predates ES5, when the thisArg was added;
>> and also because a well-behaved comparator only operates based on `a` and
>> `b` - why would you need a receiver?
>>
>> On Mon, Nov 11, 2019 at 7:34 PM Michaël Rouges <michael.rouges at gmail.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> Is there a reason to not have a `thisArg ` for the
>>> `Array.prototype.sort()` callback?
>>>
>>> Actually, it enforces to bind the context or to have nested functions,
>>> each one creating a new function where it isn't strictly necessary.
>>>
>>> Michaël Rouges - https://github.com/Lcfvs - @Lcfvs
>>> _______________________________________________
>>> es-discuss mailing list
>>> es-discuss at mozilla.org
>>> https://mail.mozilla.org/listinfo/es-discuss
>>>
>> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20191111/72f90e71/attachment-0001.html>


More information about the es-discuss mailing list