RE: How to correctly spec sequences requiring an iterable from Domenic Denicola on 2013-11-15 (public-script-coord@w3.org from October to December 2013)

From: Domenic Denicola <domenic@domenicdenicola.com>
Date: Fri, 15 Nov 2013 17:58:50 +0000
To: Allen Wirfs-Brock <allen@wirfs-brock.com>, Boris Zbarsky <bzbarsky@MIT.EDU>
CC: Jason Orendorff <jason.orendorff@gmail.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <cf0b66915eba44a69994b32184369110@BN1PR05MB325.namprd05.prod.outlook.com>

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 17:59:20 UTC