That's not gonna happen until when/if Haskell supports name/operator overloading. There's a scarcity of good symbols/function names and everyone wants to use them. So naturally, type class abuse follows.

Regards,

John A. De Goes
N-Brain, Inc.
The Evolution of Collaboration

http://www.n-brain.net    |    877-376-2724 x 101

On Oct 5, 2009, at 7:12 AM, Miguel Mitrofanov wrote:



Sönke Hahn wrote:

I used to implement
   fromInteger n = (r, r) where r = fromInteger n
, but thinking about it,     fromInteger n = (fromInteger n, 0)
seems very reasonable, too.

Stop pretending something is a number when it's not.
_______________________________________________
Haskell-Cafe mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/haskell-cafe

_______________________________________________
Haskell-Cafe mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/haskell-cafe

Reply via email to