Kent Johnson wrote:
On Wed, Jun 24, 2009 at 11:32 PM, Dave C 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
On Wed, Jun 24, 2009 at 11:32 PM, Dave C 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 circui
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, akin to:
False and produces_side_eff