On Wed, Jun 24, 2009 at 11:32 PM, Dave C<[email protected]> wrote: > Hi > I've read that the builtin all() function stops evaluating as soon as > it hits a false item, meaning that items after the first false one are > not evaluated. > > I was wondering if someone could give an example of where all()'s > short circuiting is of consequence
It can have a performance impact if the sequence under test is long or the comparison is expensive. Kent _______________________________________________ Tutor maillist - [email protected] http://mail.python.org/mailman/listinfo/tutor
