(how to avoid multiple instances)
|(2 intermediate revisions by one user not shown)|
Latest revision as of 15:43, 20 January 2009
 1 Question
I like to define multiple type class instances for the same pair of class and type. Sometimes I also need two instances where the order of type parameters is different.E.g. I want to define two
One instance where the first member is mapped and another instance where the second member is mapped. How is it possible?
 2 Answer
You can achieve the first goal if you keep class and type definitions in other modules than the instance declarations. These instances are then called orphan instances. However you won't be lucky with this solution, since you must ensure, that two modules with conflicting instances declarations are never imported together, since instance declarations are automatically imported and cannot be hidden. Even more also modules which import conflicting modules only indirectly conflict itself. The second problem cannot be solved with this approach, too.
Thus multiple instances should be avoided, and a safe way to do this is to avoid orphan instances.You can achieve this by wrapping the type in a
If you do not fear language extensions you can simplify this task considerably using the
The custom instance can be defined for the class/newtype pair and it is not orphan, if it is defined where newtype is introduced.
Example: There are so many types and operations that exhibit a monoid structure,but it would not be useful to call all the operations