- From: Brendan Eich <brendan@mozilla.org>
- Date: Fri, 15 Nov 2013 10:12:00 -0800
- To: Domenic Denicola <domenic@domenicdenicola.com>
- Cc: Allen Wirfs-Brock <allen@wirfs-brock.com>, Boris Zbarsky <bzbarsky@MIT.EDU>, Jason Orendorff <jason.orendorff@gmail.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Jason should weigh in, but I favor for-of working on strings. They are array-like albeit frozen.
On null or undefined, I see no need for the null disjunct. Precedent outside of null == undefined is lacking - particularly for a protocol (interface) test of this kind.
/be
> On Nov 15, 2013, at 9:58 AM, Domenic Denicola <domenic@domenicdenicola.com> wrote:
>
> From: Allen Wirfs-Brock <allen@wirfs-brock.com>
>
>> As current spec'ed GetIterator("primitiveString") does in fact work with primitive strings. So, any conditional Iterable test also needs to consider a primitive string to be an Iterable. This isn't currently correctly handled in the ES6 spec. It's a new bug that I will fix.
>
> Sorry, I wasn't quite clear---what do you consider correct, and what do you consider a bug? Is `for`-`of` supposed to work with strings? What about `Array.from`? What about `Promise.all`?
>
>
>
Received on Friday, 15 November 2013 18:12:34 UTC