Halo nucleus

Epigram is the name of a functional programming language with dependent types. Epigram also refers to the IDE usually packaged with the language. Epigram's type system is strong enough to express program specifications. The goal is to support a smooth transition from ordinary programming to integrated programs and proofs whose correctness can be checked and certified by the compiler. Epigram exploits the propositions as types principle, and is based on intuitionistic type theory.

The Epigram prototype was implemented by Conor McBride based on joint work with James McKinna. Its development is continued by the Epigram group in Nottingham, Durham, St Andrews and Royal Holloway in the UK. The current experimental implementation of the Epigram system is freely available together with a user manual, a tutorial and some background material. The system has been used under Linux, Windows and Mac OS X.

It is currently unmaintained, and version 2, which was intended to implement Observational Type Theory, was never released.

Syntax

Epigram uses a two-dimensional syntax, with a LaTeX version and an ASCII version. Here are some examples from The Epigram Tutorial:

Examples

The natural numbers

The following declaration defines the natural numbers:

     (         !       (          !   (  n : Nat  !
data !---------! where !----------! ; !-----------!
     ! Nat : * )       !zero : Nat)   !suc n : Nat)

The declaration says that Nat is a type with kind * (i.e., it is a simple type) and two constructors: zero and suc. The constructor suc takes a single Nat argument and returns a Nat. This is equivalent to the Haskell declaration "data Nat = Zero | Suc Nat".

In LaTeX, the code is displayed as:

$\underset{\_}{\mathrm{d}\mathrm{a}\mathrm{t}\mathrm{a}}\left(\frac{}{\mathsf{N}\mathsf{a}\mathsf{t}:\star }\right)\underset{\_}{\mathrm{w}\mathrm{h}\mathrm{e}\mathrm{r}\mathrm{e}}\left(\frac{}{\mathsf{z}\mathsf{e}\mathsf{r}\mathsf{o}:\mathsf{N}\mathsf{a}\mathsf{t}}\right);\left(\frac{n:\mathsf{N}\mathsf{a}\mathsf{t}}{\mathsf{s}\mathsf{u}\mathsf{c}n:\mathsf{N}\mathsf{a}\mathsf{t}}\right)$

Recursion on naturals

$\mathsf{N}\mathsf{a}\mathsf{t}\mathsf{I}\mathsf{n}\mathsf{d}:\begin{array}{c}\mathrm{\forall }P:\mathsf{N}\mathsf{a}\mathsf{t}\to \star \Rightarrow P\mathsf{z}\mathsf{e}\mathsf{r}\mathsf{o}\to \\ (\mathrm{\forall }n:\mathsf{N}\mathsf{a}\mathsf{t}\Rightarrow Pn\to P(\mathsf{s}\mathsf{u}\mathsf{c}n))\to \\ \mathrm{\forall }n:\mathsf{N}\mathsf{a}\mathsf{t}\Rightarrow Pn\end{array}$

$\mathsf{N}\mathsf{a}\mathsf{t}\mathsf{I}\mathsf{n}\mathsf{d}Pmzms\mathsf{z}\mathsf{e}\mathsf{r}\mathsf{o}\equiv mz$

$\mathsf{N}\mathsf{a}\mathsf{t}\mathsf{I}\mathsf{n}\mathsf{d}Pmzms(\mathsf{s}\mathsf{u}\mathsf{c}n)\equiv msn(NatIndPmzmsn)$

...And in ASCII:

NatInd : all P : Nat -> * => P zero ->
         (all n : Nat => P n -> P (suc n)) ->
         all n : Nat => P n
NatInd P mz ms zero => mz
NatInd P mz ms (suc n) => ms n (NatInd P mz ms n)

Addition

$\mathsf{p}\mathsf{l}\mathsf{u}\mathsf{s}xy\Leftarrow \underset{\_}{\mathrm{r}\mathrm{e}\mathrm{c}}x\{$

$\mathsf{p}\mathsf{l}\mathsf{u}\mathsf{s}xy\Leftarrow \underset{\_}{\mathrm{c}\mathrm{a}\mathrm{s}\mathrm{e}}x\{$

$\mathsf{p}\mathsf{l}\mathsf{u}\mathsf{s}\mathsf{z}\mathsf{e}\mathsf{r}\mathsf{o}y\Rightarrow y$

$\mathsf{p}\mathsf{l}\mathsf{u}\mathsf{s}(\mathsf{s}\mathsf{u}\mathsf{c}x)y\Rightarrow suc(\mathsf{p}\mathsf{l}\mathsf{u}\mathsf{s}xy)\}\}$

...And in ASCII:

plus x y <= rec x {
  plus x y <= case x {
    plus zero y => y
    plus (suc x) y => suc (plus x y)
  }
}

Dependent types

Epigram is essentially a typed lambda calculus with generalized algebraic data type extensions, except for two extensions. First, types are first-class entities, of type $\star$; types are arbitrary expressions of type $\star$, and type equivalence is defined in terms of the types' normal forms. Second, it has a dependent function type; instead of $P\to Q$, $\mathrm{\forall }x:P\Rightarrow Q$, where $x$ is bound in $Q$ to the value that the function's argument (of type $P$) eventually takes.

Full dependent types, as implemented in Epigram, are a powerful abstraction. (Unlike in Dependent ML, the value(s) depended upon may be of any valid type.) A sample of the new formal specification capabilities dependent types bring may be found in The Epigram Tutorial.

See also

• Alf, a proof assistant among the predecessors of Epigram.

Further reading

• Conor McBride and James McKinna (2004), The view from the left, Journal of Functional Programming
• Conor McBride (2004), The Epigram Prototype, a nod and two winks
• Conor McBride (2004), The Epigram Tutorial
• Thorsten Altenkirch, Conor McBride and James McKinna (2005), Why Dependent Types Matter

External links

• EPSRC on ALF, lego and related

References

43 year old Petroleum Engineer Harry from Deep River, usually spends time with hobbies and interests like renting movies, property developers in singapore new condominium and vehicle racing. Constantly enjoys going to destinations like Camino Real de Tierra Adentro.