I have never run into such an issue. Typically classes tend to have the
smallest possible basis of methods. I would consider a class with more than
about 10 or 15 methods (including superclasses' methods) to indicate poor
design. That is just a rough heuristic.
But you're right, it would be
It's not that I like to have a lot of methods in a class, but
rather a lot of classes.
--
_jsn
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
No deep inheritance? Then what's the problem?
module X where
class Foo a where foo :: a - String
module Y where
class Foo' a where foo :: a - String
module Main where
import qualified X
import qualified Y
instance X.Foo Int where foo _ = X
instance Y.Foo' Int where foo _ = Y
It is known that
Oh! Then there is no problem, after all.
--
_jsn
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
