Well, it's clearly a design choice. But in general laziness does not come for free. The choice made by the Haskell designers was that the 'array' function can consume and explore all its input before producing any result. It just give more scope to the implementor. Nothing too deep.
Simon | -----Original Message----- | From: Johannes Waldmann [mailto:[EMAIL PROTECTED]] | Sent: 12 November 2001 20:29 | To: [EMAIL PROTECTED] | Subject: how strict is Array.array? | | | I was surprised to note that | | bounds $ array (0,1) undefined | | is undefined ( rather than (0,1) ) - why is this? | | just curious, | -- | -- Johannes Waldmann ---- | http://www.informatik.uni-leipzig.de/~joe/ -- | -- | [EMAIL PROTECTED] -- phone/fax (+49) 341 9732 204/252 -- | | _______________________________________________ | Haskell mailing list | [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/haskell | _______________________________________________ Haskell mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/haskell
