Re: Why does this blow the stack?

On 12/26/07, Don Stewart <dons <at> galois.com> wrote:
> Depending on laziness if fine, but depending on undefined strictness semantics
> for particular types is more fragile.  Whether Int or Bool or whatever
> type has a strict or lazy accumulator in enumFromTo is entirely
> unspecified -- you can't look up the report to check.

Right, I understand that.  But is there any reason not to keep the
Integer version of [a..] lazy, given that we can fix the stack
overflow problem without introducing strictness?