On Sep 11, 2012, at 1:07 AM, Cameron McCormack wrote:
> Arun Ranganathan:
>> I've pinged heycam to see if this is a proper use of the sequence type. I'm
>> not sure it allows for such a variation in parameters.
>
> I agree with Boris, it makes sense to use sequence<> here. Whenever you just
Arun Ranganathan:
I've pinged heycam to see if this is a proper use of the sequence type. I'm
not sure it allows for such a variation in parameters.
I agree with Boris, it makes sense to use sequence<> here. Whenever you
just want to take a list of values in an operation argument, and you
On 9/10/12 6:36 PM, Arun Ranganathan wrote:
I've pinged heycam to see if this is a proper use of the sequence type. I'm
not sure it allows for such a variation in parameters.
Sequence allows any WebIDL type as a sequence element.
So for example, you can do this:
sequence<(sequence<(DOMStr
I've pinged heycam to see if this is a proper use of the sequence type. I'm
not sure it allows for such a variation in parameters.
-- A*
On Sep 9, 2012, at 2:31 PM, Boris Zbarsky wrote:
> On 9/9/12 12:13 PM, Glenn Maynard wrote:
>>In particular, a Blob represents immutable binary data. Th
On 9/9/12 12:13 PM, Glenn Maynard wrote:
In particular, a Blob represents immutable binary data. That means
that it has to copy the input anyway. Given that, it doesn't make
sense to pass the input by reference if the caller _does_ happen to
have an WebIDL array object.
That do
On Sun, Sep 9, 2012 at 9:34 AM, Boris Zbarsky wrote:
> In particular, a Blob represents immutable binary data. That means that
> it has to copy the input anyway. Given that, it doesn't make sense to pass
> the input by reference if the caller _does_ happen to have an WebIDL array
> object.
>
T
In particular, a Blob represents immutable binary data. That means that
it has to copy the input anyway. Given that, it doesn't make sense to
pass the input by reference if the caller _does_ happen to have an
WebIDL array object.
But worse yet, actual real-life callers call this with JS arra
