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

[Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values

From: <bugzilla@jessica.w3.org>
Date: Wed, 01 Oct 2014 12:36:12 +0000
To: public-script-coord@w3.org
Message-ID: <bug-26183-3890-VpWq6n9wKk@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26183

--- Comment #17 from Anne <annevk@annevk.nl> ---
That seems nice, but not sufficient for my three multimaps. FormData,
URLSearchParams, and Headers, all have an associated list of sorts where each
entry consists of a name and a value.

I should be able to easily explain what the list is, what the keys/names are,
and what the values, and then based on that IDL can "generate" keys(),
values(), and Symbol.iterator behavior.

Does that make sense? If you disagree I guess I could also define keys(),
values(), entries() etc. on my own but then it seems I would like some kind of
hook so I can define these methods to return iterators. (I could even see me
defining this as some kind of MultiMapIterator mixin that I have implemented by
each object. Then maybe later it can be uplifted to IDL.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 1 October 2014 12:36:18 UTC

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