In computer science and logic, a dependent type is a type that depends on a value. It is an overlapping feature of math-encoding type theory and bug-stopping type systems. In intuitionistic type theory, dependent types are used to encode logic's quantifiers like "for all" and "there exists". In functional programming languages like ATS, Agda, Idris and Epigram, dependent types prevent bugs by allowing very expressive types.
Two common examples of dependent types are dependent functions and dependent pairs. A dependent function's return type may depend on the value (not just type) of an argument. A function that takes a positive integer "n" may return an array of length "n". (Note that this is different from polymorphism where the type is an argument.) A dependent pair may have a second value that depends on the first. It can be used to encode a pair of integers where the second one is greater than the first.
Dependent types add complexity to a type system. Deciding the equality of dependent types in a program may require computations. If arbitrary values are allowed in dependent types, then deciding type equality may involve deciding whether two arbitrary programs produce the same result; hence type checking may become undecidable.
- 1 History
- 2 Formal definition
- 3 Dependent pair type
- 4 Systems of the lambda cube
- 5 Simultaneous Programming language and Logic
- 6 Comparison of languages with dependent types
- 7 See also
- 8 Footnotes
- 9 References
- 10 Further reading
- 11 External
Dependent types were created to deepen the connection between programming and logic.
In 1934, Haskell Curry noticed that the types used in mathematic programming languages followed the same pattern as axioms in propositional logic. Going further, for every proof in the logic, there was a matching function (term) in the programming language. One of Curry's examples was the correspondence between simply typed lambda calculus and intuitionistic logic.
Predicate logic is an extension of propositional logic, adding quantifiers. Howard and de Bruijn extended lambda calculus to match this more powerful logic by creating types for dependent functions, which correspond to "for all", and dependent pairs, which correspond to "there exists".
(Because of this and other work by Howard, propositions-as-types is known as the Curry-Howard correspondence.)
Dependent types can be, very loosely speaking, imagined to be similar to the type of an indexed family of sets. More formally, given a type in a universe of types , one may have a family of types which assigns to each term a type . A function whose codomain varies depending on its argument is a dependent function, and the type of this function is called a dependent type, dependent product type or pi-type. For this example, the dependent type would be written as
If B is a constant, the dependent type becomes an ordinary function . That is, is judgementally equal to the function type .
For example, writing for -tuples of real numbers, then would be the type of functions which, given a natural number n, return a tuple of real numbers of size n. The usual function space arises as a special case when the range type does not actually depend on the input, e.g. is the type of functions from natural numbers to the real numbers, which is written as in the simply typed lambda calculus.
Polymorphic functions are an important example of dependent functions, that is, functions having dependent type. Given a type, these functions act on elements of that type (or on elements of a type constructed (derived, inherited) from that type). A polymorphic function returning elements of type C would have a polymorphic type written as
Dependent pair type
The opposite of the dependent type is the dependent pair type, dependent sum type or sigma-type. It is analogous to the coproduct or disjoint union. Sigma-types can also be understood as models of existential quantifiers. Notationally, it is written as
The dependent pair type captures the idea of a pair, where the type of the second term is dependent on the first. Thus, if
then and . If B is a constant, then the dependent pair type becomes (is judgementally equal to) the product type, that is, an ordinary Cartesian product .
Systems of the lambda cube
Henk Barendregt developed the lambda cube as a means of classifying type systems along three axes. The eight corners of the resulting cube-shaped diagram each correspond to a type system, with simply typed lambda calculus in the least expressive corner, and calculus of constructions in the most expressive. The three axes of the cube correspond to three different augmentations of the simply typed lambda calculus: the addition of dependent types, the addition of polymorphism, and the addition of higher kinded type constructors (functions from types to types, for example). The lambda cube is generalized further by pure type systems.
First order dependent type theory
The system of pure first order dependent types, corresponding to the logical framework LF, is obtained by generalising the function space type of the simply typed lambda calculus to the dependent product type.
Second order dependent type theory
The system of second order dependent types is obtained from by allowing quantification over type constructors. In this theory the dependent product operator subsumes both the operator of simply typed lambda calculus and the binder of System F.
Higher order dependently typed polymorphic lambda calculus
The higher order system extends to all four forms of abstraction from the lambda cube: functions from terms to terms, types to types, terms to types and types to terms. The system corresponds to the Calculus of constructions whose derivative, the calculus of inductive constructions is the underlying system of the Coq proof assistant.
Simultaneous Programming language and Logic
The Curry–Howard correspondence implies that types can be constructed that express arbitrarily complex mathematical properties. If the user can supply a constructive proof that a type is inhabited (i.e., that a value of that type exists) then a compiler can check the proof and convert it into executable computer code that computes the value by carrying out the construction. The proof checking feature makes dependently typed languages closely related to proof assistants. The code-generation aspect provides a powerful approach to formal program verification and proof-carrying code, since the code is derived directly from a mechanically verified mathematical proof.
Comparison of languages with dependent types
|Language||Actively developed||Paradigm[fn 1]||Tactics||Proof terms||Termination checking||Types can depend on[fn 2]||Universes||Proof irrelevance||Program extraction||Extraction erases irrelevant terms|
|ATS||Yes||Functional / imperative||No||Yes||Yes||?||?||?||Yes||?|
|Cayenne||No||Purely functional||No||Yes||No||Any term||No||No||?||?|
|Coq||Yes||Purely functional||Yes||Yes||Yes||Any term||Yes[fn 5]||No||Haskell, Scheme and OCaml||Yes|
|Dependent ML||No[fn 6]||?||?||Yes||?||Natural numbers||?||?||?||?|
|Guru||No||Purely functional||hypjoin||Yes||Yes||Any term||No||Yes||Carraway||Yes|
|Idris||Yes||Purely functional||Yes||Yes||Yes (optional)||Any term||Yes||No||Yes||Yes, aggressively|
|Matita||Yes||Purely functional||Yes||Yes||Yes||Any term||Yes||Yes||OCaml||Yes|
|NuPRL||Yes||Purely functional||Yes||Yes||Yes||Any term||Yes||?||Yes||?|
|Twelf||Yes||Logic programming||?||Yes||Yes (optional)||Any (LF) term||No||No||?||?|
- This refers to the core language, not to any tactic or code generation sublanguage.
- Subject to semantic constraints, such as universe constraints
- Ring solver
- Optional universes, optional universe polymorphism, and optional explicitly specified universes
- Universes, automatically inferred universe constraints (not the same as Agda's universe polymorphism) and optional explicit printing of universe constraints
- Has been superseded by ATS
- Sørensen, Morten Heine B.; Pawel Urzyczyn (1998). Lectures on the Curry-Howard Isomorphism.
- Bove, Ana; Peter Dybjer (2008). Dependent Types at Work.
- "Agda download page".
- "Agda Ring Solver".
- "Announce: Agda 2.2.8".
- "ATS Changelog".
- "email from ATS inventor Hongwei Xi".
- "Coq CHANGES in Subversion repository".
- "Guru SVN".
- Aaron Stump (6 April 2009). "Verified Programming in Guru". Retrieved 28 September 2010.
- Adam Petcher (1 April 2008). "Deciding Joinability Modulo Ground Equations in Operational Type Theory". Retrieved 14 October 2010.
- "Idris git repository".
- "Idris, a language with dependent types - extended abstract".
- Edwin Brady. "How does Idris compare to other dependently-typed programming languages?".
- "Matita SVN".
- "Xanadu home page".
- Martin-Löf, Per (1984). Intuitionistic Type Theory. Bibliopolis.
- Nordström, Bengt; Petersson, Kent; Smith, Jan M. (1990). Programming in Martin-Löf's Type Theory: An Introduction. Oxford University Press.
- Barendregt, Henk (1992). "Lambda calculi with types". In S. Abramsky, D. Gabbay and T. Maibaum. Handbook of Logic in Computer Science. Oxford Science Publications.
- McBride, Conor; McKinna, James (January 2004). "The view from the left". Journal of Functional Programming 14 (1): 69–111. doi:10.1017/s0956796803004829.
- Altenkirch, Thorsten; McBride, Conor; McKinna, James (April 2005). Why dependent types matter.
- Norell, Ulf. Towards a practical programming language based on dependent type theory. PhD thesis, Department of Computer Science and Engineering, Chalmers University of Technology, SE-412 96 Göteborg, Sweden, September 2007.
- Oury, Nicolas and Swierstra, Wouter (2008). "The Power of Pi". Accepted for presentation at ICFP, 2008.
- Norell, Ulf (2008). Dependently Typed Programming in Agda.
- Dependently Typed Programming 2008
- Dependently Typed Programming 2010
- Dependently Typed Programming 2011
- "Dependent type" at the Haskell Wiki
- dependent type theory in nLab
- dependent type in nLab
- dependent product type in nLab
- dependent sum type in nLab
- dependent product in nLab
- dependent sum in nLab