On Thu, 21 Mar 2013 21:55:10 -0400
"Jonathan M Davis" <jmdavisp...@gmx.com> wrote:

> Anything else would be a change that would
> have to be discussed, so specifically testing that a conformant range
> throws a RangeError from popFront when it's empty (as Nick was
> suggesting) would not be correct at this point.
> 

I wasn't suggesting that, merely trying to list a bunch of examples of
testable things. Clearly I got a few of the examples wrong ;)

But that does kinda speak to the usefulness of having something
standard that can be expected to actually do the *correct* tests,
instead of all range authors just winging it on their own and
potentially misunderstanding the rules.

Reply via email to