- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Thu, 06 Jun 2013 11:53:44 -0400
- To: Anne van Kesteren <annevk@annevk.nl>
- CC: Cameron McCormack <cam@mcc.id.au>, DOM mailing list <www-dom@w3.org>
On 6/6/13 7:12 AM, Anne van Kesteren wrote:
> The behavior we want is equivalent to:
>
> function accept(value) { ... }
> accept()
>
> Which will result in value being undefined.
Sure, but the question is what arguments.length ends up being. That's
the only difference between "missing argument" and "argument explicitly
passed as undefined" in JS.
If we plan to always pass explicit undefined to callbacks when we were
accepted with no value, then we should make the callbacks take a
non-optional "any", since they will in fact always get one.
-Boris
Received on Thursday, 6 June 2013 15:54:14 UTC