An orphan instance is a type class instance for class C and type T which is neither defined in the module where C is defined nor in the module where T is defined.
Type class instances are special in that they don't have a name and cannot be imported explicitly. This also means that they cannot be excluded explicitly. All instances defined in a module A are imported automatically when importing A, or importing any module that imports A, directly or indirectly.
Say you want to define an alternative instance to an existing instance. This is a bad thing, since if two instances for the same class/type pair are in scope, then you cannot describe in Haskell 98 which instance to use. If you want to use multiple instances for the same class/type, you have to ensure that they are never imported together in a module somewhen. It is almost impossible to assert that, or put differently, it would reduce the composability of libraries considerably.
Monad instance of
Either is a good example.
It is not defined where
Either is defined, thus all of its
Monad instances must be orphan.
Instead it is defined both in
Control.Monad.Error of the Monad Transformer Library
Control.Monad.Trans.Error of its lightweight cousin the 'transformers' package.
Since some packages use MTL and others 'transformers' it becomes difficult to use that instance at all,
although both instances are equivalent!
The explicit-exception package with its
Exceptional might be a better choice to use since it avoids the current problem with orphan Monad instances of
Actually, non-orphan instances can avoid definition of multiple instances. For defining an instance you have to import the class and the type and then you will automatically have the according non-orphan instances imported, too. If you want to define a new instance then the compiler will reject it immediately.
A last advice: If you encounter a missing instance for a class or a type of a package, resist to define your own orphan instance, because it will likely collide with such instances of other packages, or it will collide with new instances added in later versions of that package. Instead ask the package author to add your instance. Sometimes it turns out that the instance was not included for the good reason that there is more than one reasonable instance definition. If your instance cannot be included, follow the advices in the article about multiple instances.
- Multiple instances
- Libraries mailing list on Orphan instances can be good
- Ideas on possible compiler warnings for coping with orphan instances
- Libraries mailing list on Relaxin the PVP with regards to adding instances
- Partial Revelation feature of Modula-3 which causes similar problems like Haskell's type class instances