# Data declaration with constraint

### From HaskellWiki

(Difference between revisions)

(maybe multi-parameter type classes are a way out) |
(Added use of GADTs to add a context to data constructors.) |
||

Line 20: | Line 20: | ||

=== Answer === |
=== Answer === |
||

− | Only functions can have type constraints. |
+ | In Haskell 98, only functions can have type constraints. |

The type constraint of a <hask>data</hask> only refers to the constructors. |
The type constraint of a <hask>data</hask> only refers to the constructors. |
||

The designers of Haskell 98 do now think, that it was a bad decision to allow constraints on constructors. |
The designers of Haskell 98 do now think, that it was a bad decision to allow constraints on constructors. |
||

Line 26: | Line 26: | ||

== Solution == |
== Solution == |
||

− | But how can one bake type constraints into a type? |
+ | You could use ghc's [http://www.haskell.org/ghc/docs/latest/html/users_guide/data-type-extensions.html#gadt-style Generalised Algebraic Data Structures (GADTs)] to add an implicit context to the data constructors. |

− | You cannot. One should insert a discussion here, whether it is sensible to want this. |
||

− | For now you have to stick to [[multi-parameter type class]]es, |
+ | There has been some discussion about whether it is sensible to want this. |

− | where <hask>T a</hask> and <hask>a</hask> are separate arguments. |
+ | |

+ | A Haskell 98 workaround is to use [[multi-parameter type class]]es, where <hask>T a</hask> and <hask>a</hask> are separate arguments. |
||

## Latest revision as of 23:07, 4 June 2013

## Contents |

## [edit] 1 Problem

### [edit] 1.1 Question

I have declared

data C a => T a = Cons a

and I hoped that now the type checker knows,

that every value of typeT a

a

T

T

E.g.

instance Vector T where add (Cons x) (Cons y) = Cons (x+y) -- requires Num constraint on type a

### [edit] 1.2 Answer

In Haskell 98, only functions can have type constraints.

The type constraint of adata

The designers of Haskell 98 do now think, that it was a bad decision to allow constraints on constructors.

## [edit] 2 Solution

You could use ghc's Generalised Algebraic Data Structures (GADTs) to add an implicit context to the data constructors.

There has been some discussion about whether it is sensible to want this.

A Haskell 98 workaround is to use multi-parameter type classes, whereT a

a

## [edit] 3 See also

- Henning Thielemann in Haskell-Cafe: Context for type parameters of type constructors
- Mark Nicholls in Haskell-Cafe: nice simple problem for someone struggling....