W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2013

Re: sequence and iterables

From: Jonas Sicking <jonas@sicking.cc>
Date: Fri, 15 Nov 2013 18:33:34 -0800
Message-ID: <CA+c2ei9XOQ+WbR=jUSe-R+OhQF-wOZzuQPc4_rc171T3Kjj9ow@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Anne van Kesteren <annevk@annevk.nl>
On Fri, Nov 15, 2013 at 6:30 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 11/15/13 9:28 PM, Tab Atkins Jr. wrote:
>>
>> Slightly, when you're just going to run through the iterable
>> immediately.  It's normal if you're going to store the data for
>> whatever reason.
>
> Most WebIDL stuff does run through it immediately, I would think, to do the
> type coercion/checking.  The only possible exception would be sequence<any>.

Type coersion is a good example. I hadn't thought of that. Makes a lot
of sense to me to define that sequence<T> type-coerces and iterates at
the same time.

Are there other examples? In particular, are there examples once you
are past the WebIDL layer?

/ Jonas
Received on Saturday, 16 November 2013 02:34:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:19 UTC