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: Fri, 03 Oct 2014 14:12:18 +0000
To: public-script-coord@w3.org
Message-ID: <bug-26183-3890-M6YQMtrhjS@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26183

--- Comment #31 from Tab Atkins Jr. <jackalmage@gmail.com> ---
(In reply to Anne from comment #30)
> Putting Map/Set on the prototype is not what TC39 wants. We should not do
> it. We should just port new methods as they come in and at some point traits
> will hopefully make things better.

Has TC39 explicitly said that, or just Domenic?

Once again, my concern is not new Map methods (those won't work anyway, since
they interact with [[MapData]] directly; IDL is always going to need to port
them over with our custom delegating definition).  It's about author-defined
methods on Map, which operate via the built-in methods, and it would be
unfortunate if those didn't work on map-likes.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 3 October 2014 14:12:20 UTC

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