Original-Via: uk.ac.nsf; Sun, 10 Nov 91 18:58:02 GMT
I was originally going to stay out of this one, but here's why I'm
voting for explicit superclass declarations.
The problem I see is that allowing implicit class declarations is
bound to cause confusion when a user does not actually see an ent
Original-Via: uk.ac.nsf; Sun, 10 Nov 91 16:03:39 GMT
Original-Sender: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
| From: john peterson <[EMAIL PROTECTED]>
| I'll still stick with my opinion on this one, though. Here's more
| reasons:
| a) This represents a potentially large numb
Original-Via: uk.ac.nsf; Sun, 10 Nov 91 07:55:42 GMT
Paul Hudak writes:
I don't understand your example.
That's because it's *wrong*! I was obviously thinking of Haskell 2,
where the relaxation of the C-T rule allows me to put instance
declarations somewhere besides the defining modules of th
Original-Via: uk.ac.nsf; Sun, 10 Nov 91 02:23:26 GMT
a) If an instance declaration is given for a type T and class C, instance
declarations must also be given for T and all the superclasses of C.
b) If an instance declaration is given for a type T and class C, T is
automatically an i
