Re: Removing the concept of "optional any"

On 2/19/14 12:26 PM, Boris Zbarsky wrote:
> If so, it seems like that behavior would more or less map to:
>
> 1)  "any" is allowed, affects .length if trailing, accepts all ES
> values, does NOT trigger an argc check.  Defaults to undefined if not
> passed explicitly.
>
> 2)  "optional any" is allowed, does not affect .length if trailing,
> accepts all ES values, defaults to the provided default value, or
> undefined if no default value is provided, if not passed explicitly.

So does this make sense to people?  I'd like to actually move forward 
here, one way or another.

-Boris

Received on Wednesday, 5 March 2014 14:36:50 UTC