[Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values from bugzilla@jessica.w3.org on 2014-06-24 (public-script-coord@w3.org from April to June 2014)

From: <bugzilla@jessica.w3.org>
Date: Tue, 24 Jun 2014 07:32:04 +0000
To: public-script-coord@w3.org
Message-ID: <bug-26183-3890-p7MAOkMuMW@http.www.w3.org/Bugs/Public/>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26183

Anne <annevk@annevk.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |annevk@annevk.nl
         Depends on|                            |17648

--- Comment #1 from Anne <annevk@annevk.nl> ---
Note that we might want to represent these values using different objects. E.g.
FormData internally has a list of values that are tuples. And when iterating
over them we want these to be arrays. (We should also make it clear whether
those arrays are reused or are fresh each time. Fresh each time seems easiest.)

Note that we should also be clear with respect to whether the iterator returns
a snapshot of the underlying data or not. Maybe with syntax? E.g. for NodeList
the current idea is for the iterator to be live (match the semantics of the
object), but I suspect most others we would like it to be static.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Tuesday, 24 June 2014 07:32:06 UTC