Hi Ivan, > Another possible argument: large type classes can look daunting for > both implementors and users, even if only one or two methods need to > be defined for a minimal instantiation (I'm tring to work out what to > do here myself, as I have some typeclasses that for efficiency reasons > it might be nice to have more methods in the class, but it makes it a > little overwhelming).
But by putting just a small part of the interface into the class does not make the live of a user any simpler. The user usually has to know the whole interface of the module. Or am I missing something? Cheers, Uwe _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
