Personal tools

Multi-parameter type class

From HaskellWiki

(Difference between revisions)
Jump to: navigation, search
(basics)
 
(About)
(4 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
[[Category:Language extensions]]
 
[[Category:Language extensions]]
  +
[[Category:Glossary]]
 
[[Category:Stub articles]]
 
[[Category:Stub articles]]
  +
== About ==
   
  +
Basically, [[type class|type classes]] which can take multiple arguments, such as:
   
== About ==
+
<haskell>
  +
class Monad m => VarMonad m v where
  +
new :: a -> m (v a)
  +
get :: v a -> m a
  +
put :: v a -> a -> m ()
  +
  +
instance VarMonad IO IORef where ...
  +
instance VarMonad (ST s) (STRef s) where ...
  +
</haskell>
  +
  +
To enable them, use the <hask>{-# LANGUAGE MultiParamTypeClasses #-}</hask> pragma.
   
Basically, type classes which can take multiple arguments, such as:
+
If you think of a single-parameter type class as a set of types, then a multi-parameter type class is a relation between types.
   
<hask>
+
Naive use of MPTCs may result in ambiguity, so [[functional dependencies]] were developed as a method of resolving that ambiguity, declaring that some subset of the parameters is sufficient to determine the values of the others.
class Foo a b
 
</hask>
 
   
Without [[Functional dependencies]] or [[Associated types]], these multi-parameter type classes may cause too much ambiguity to pass the type-checker.
+
Some uses of MPTCs with functional dependencies can be replaced with [[type families]].
   
 
== Also see ==
 
== Also see ==

Revision as of 17:19, 21 December 2012

1 About

Basically, type classes which can take multiple arguments, such as:

class Monad m => VarMonad m v where
  new :: a -> m (v a)
  get :: v a -> m a
  put :: v a -> a -> m ()
 
instance VarMonad IO IORef where ...
instance VarMonad (ST s) (STRef s) where ...
To enable them, use the
{-# LANGUAGE MultiParamTypeClasses #-}
pragma.

If you think of a single-parameter type class as a set of types, then a multi-parameter type class is a relation between types.

Naive use of MPTCs may result in ambiguity, so functional dependencies were developed as a method of resolving that ambiguity, declaring that some subset of the parameters is sufficient to determine the values of the others.

Some uses of MPTCs with functional dependencies can be replaced with type families.

2 Also see

The Haskell' page