Re: How to correctly spec sequences requiring an iterable

Some people prefer to use an explicit null to state that they really mean "not the normal object value" rather than the bit more sloppy use of undefined.  I happy to define things in a way that accommodates that either style.


On Nov 15, 2013, at 9:33 AM, Domenic Denicola wrote:

> From: Allen Wirfs-Brock <>
>> If iteratorGetter is undefined or null then let usingIterator be false; otherwise let usingIterator be true.
> Why "or null"? I would expect one of these two alternatives:
> 1. undefined => usingIterator = false; otherwise, true
> 2. callable => usingIterator = true; otherwise, false

Received on Friday, 15 November 2013 17:38:05 UTC