Epigram (programming language)
From Wikipedia, the free encyclopedia
Epigram is the name of a functional programming language with dependent types and of the IDE usually packaged with it. 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 from the Epigram homepage together with a user manual, a tutorial and some background material. The system has been used under Linux, Windows and Mac OS X.
Contents |
[edit] Syntax
Epigram uses a two-dimensional syntax, with a LaTeX version and an ASCII version. Here are some examples from The Epigram Tutorial:
[edit] Examples
[edit] 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:
[edit] Recursion on naturals
...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)
[edit] Addition
...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) } }
[edit] Dependent types in Epigram
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 ; types are arbitrary expressions of type , and type equivalence is defined in terms of the types' normal forms. Second, it has a dependent function type; instead of , , 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.
It is planned that the forthcoming version of Epigram, Epigram 2, will be based on Observational Type Theory (note: link is to an incomplete draft paper), a new development of constructive type theory.
[edit] See also
[edit] External links
- The home page of the Epigram project
- Conor McBride and James McKinna (2004), The view from the left (pdf), Journal of Functional Programming
- Conor McBride (2004), The Epigram Prototype, a nod and two winks (pdf)
- Conor McBride (2004), The Epigram Tutorial (pdf)
- Thorsten Altenkirch, Conor McBride and James McKinna (2005), Why Dependent Types Matter (pdf)