Difference between revisions of "Multi-parameter type class"

From HaskellWiki
Jump to navigation Jump to search
(basics)
 
(a uniform interface to mutable variables can be implemented in Haskell 98)
(5 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:
   
  +
<haskell>
== About ==
 
  +
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.
  +
  +
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.
Basically, type classes which can take multiple arguments, such as:
 
   
  +
Some uses of MPTCs with functional dependencies can be replaced with [[type families]].
<hask>
 
class Foo a b
 
</hask>
 
   
  +
The above example can even be implemented in
Without [[Functional dependencies]] or [[Associated types]], these multi-parameter type classes may cause too much ambiguity to pass the type-checker.
 
  +
[[Mutable variable|plain Haskell 98]].
   
 
== Also see ==
 
== Also see ==

Revision as of 19:01, 9 June 2013

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.

The above example can even be implemented in plain Haskell 98.

Also see

The Haskell' page