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

[Bug 26985] Remove requirement for prose around iterable<> if object has indexed properties

From: <bugzilla@jessica.w3.org>
Date: Sun, 18 Oct 2015 17:06:59 +0000
To: public-script-coord@w3.org
Message-ID: <bug-26985-3890-Nid6FBSg8P@http.www.w3.org/Bugs/Public/>

--- Comment #12 from Boris Zbarsky <bzbarsky@mit.edu> ---
If it's a Set-equivalent, why does it have an indexed getter and a .length?  It
sure quacks like an array when read, though I agree the behavior on _mutations_
isn't very arraylike.

Maybe we would have _liked_ to ship a setlike interface here, but the arraylike
thing has been implemented for a while now, so we're kinda stuck with it.

More importantly, the rules for iterable-and-indexed-props need to make sense
in general for indexed things, no matter what weirdness we have with

You are receiving this mail because:
You are on the CC list for the bug.
Received on Sunday, 18 October 2015 17:07:01 UTC

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