Self-recursion and arrow functions

Axel Rauschmayer axel at
Sat Mar 16 15:19:38 PDT 2013

OK. Thankfully, with `super`, an important use case for a function referring to itself goes away (AFAIK, `super` keeps qooxdoo and Ember in non-strict mode, they need arguments.callee).

On Mar 16, 2013, at 23:12 , Brendan Eich <brendan at> wrote:

> I wouldn't overreact. My note was simply that we should not make arrows strict by definition, and TC39 agreed. Among the "folk wisdom" reasons for avoiding strict is to have arguments.callee, but of course NFEs should be preferred in modern engines. But there's no arrow NFE form.
> /be
> Brandon Benvie wrote:
>> I think this is a better argument for introducing a new primitive for referencing the current function than for resurrecting arguments.
>> On Mar 16, 2013, at 2:29 PM, Axel Rauschmayer <axel at <mailto:axel at>> wrote:
>>> Quoting Brendan Eich in [1]:
>>>> arrows can't have intrinsic names (contrast with NFEs) so arguments.callee may be wanted, so arrows should not be strict-only.
>>> Is this really an option? Sounds messy. Like a carrot to go back to non-strict. I’d either allow arguments.callee in both modes. Or introduce a new mechanism for a function to refer to itself. I thought that `arguments` would disappear from JavaScript code over time so the latter alternative seems better.
>>> Axel
>>> [1]
>>> -- 
>>> Dr. Axel Rauschmayer
>>> axel at <mailto:axel at>
>>> home: <>
>>> twitter: <>
>>> blog: <>
>>> _______________________________________________
>>> es-discuss mailing list
>>> es-discuss at <mailto:es-discuss at>
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss at

Dr. Axel Rauschmayer
axel at


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list