Extensible record

From HaskellWiki

Proposals, implementations can be found on the FirstClassLabels page of Haskell' Wiki.

Papers and libraries[edit]

Libraries on hackage[edit]

Applications[edit]

Declarative database management[edit]

Such systems can achieve more type safety (compared to direct SQL handling). They usually formulate a relational algebra concept in a declarative language.

HaskellDB[edit]

A problem where some concepts of extensible records could be useful is described in the HaskellDB project. More precisely, the problem is described in the paper downloadable from

HaskellDB uses its own extensible record system, but see also HaskellDB#Future.

CoddFish[edit]

CoddFish is another declarative, type safe database system. As for extensible record system, it uses HList --- a Haskell library for strongly typed heterogeneous collections.

Functional Reactive Programming[edit]

FRP often makes it necessary to deal with very large tuples as arrow inputs and outputs. For example, a GUI component would receive the behavior of all its writeable properties as its input. Extensible records can therefore make FRP more usable, especially if they provide defaulting.

Grapefruit[edit]

Grapefruit uses extensible records which support pattern matching and defaulting for functional reactive GUI programming.

Related concepts[edit]

Dependent type -- as an explanation for its relatedness here, see Why Dependent Types Matter written by Thorsten Altenkirch, Conor McBride, James McKinna -- or see at least its Conclusions section (section 8, pages 18--19).

Type arithmetic seems to me also a way yielding some tastes from dependent type theory.

Relational algebra implementations usually use extensible records.