RE: How to correctly spec sequences requiring an iterable from Domenic Denicola on 2013-11-18 (public-script-coord@w3.org from October to December 2013)

From: Domenic Denicola <domenic@domenicdenicola.com>
Date: Mon, 18 Nov 2013 18:05:53 +0000
To: Boris Zbarsky <bzbarsky@MIT.EDU>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <28a5692fbf5442b3954ab8ff8dbb19aa@BN1PR05MB325.namprd05.prod.outlook.com>

From: Boris Zbarsky <bzbarsky@MIT.EDU>

> 6) Walk through with IteratorStep/IteratorValue etc, converting each sequence element before stepping to the next one.
>
> Does anyone see any obvious problems with that other than the (controversial) object check in step 1?

Does this step 6 commit implementations to two separate loops, one to convert, and then one to actually do things with the elements? It seems worrying to bake this performance cost into the spec for every sequence-using function. On the other hand, O(2n) = O(n), so maybe not a big deal...

Received on Monday, 18 November 2013 18:06:22 UTC