On Fri, 26 Jan 2007, Malcolm Wallace wrote: > Me too. It is a nice observation of a particular point in the design > space, but it is so similar to pattern guards that I would not want to > have both in the language. Pattern guards win for me, because there is > no implicit Maybe, and computation sharing is explicit. >
I'm tempted to suggest this may be akin to issues like let vs where or patterns in bindings vs explicit lambdas - examples where having both adds human-expressibility to the language. -- [EMAIL PROTECTED] A problem that's all in your head is still a problem. Brain damage is but one form of mind damage. _______________________________________________ Haskell mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell
