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

Re: How to correctly spec sequences requiring an iterable

From: Allen Wirfs-Brock <allen@wirfs-brock.com>
Date: Fri, 15 Nov 2013 09:55:58 -0800
Cc: Jason Orendorff <jason.orendorff@gmail.com>, public-script-coord@w3.org
Message-Id: <FE25F6EC-42CC-4FF2-A916-C24FB7D4D397@wirfs-brock.com>
To: Boris Zbarsky <bzbarsky@MIT.EDU>

On Nov 15, 2013, at 9:42 AM, Boris Zbarsky wrote:

>> ...
> OK.  And a primitive string, e.g., should not be considered iterable for my purposes, right?

Now, that's an interesting question.


Returns the value of
so arguably a primitive strings should be considered to be an Iteratable

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.

Received on Friday, 15 November 2013 17:56:32 UTC

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