Type theory
|
|
At the broadest level, type theory is the branch of mathematics and logic that concerns itself with classifying entities into sets called types. In this sense, it is related to the metaphysical notion of 'type'. Modern type theory was invented partly in response to Russell's paradox, and features prominently in Russell and Whitehead's Principia Mathematica.
With the rise of powerful programmable computers, and the development of programming languages for the same, type theory has found practical application in the development of programming language type systems. Definitions of "type system" in the context of programming languages vary, but the following definition due to Benjamin C. Pierce roughly corresponds to the current consensus in the type theory community:
- [A type system is a] tractable syntactic method for proving the absence of certain program behaviors by classifying phrases according to the kinds of values they compute.
(Types and Programming Languages, MIT Press, 2002)
In other words, a type system divides program values into sets called types (this is called a "type assignment"), and makes certain program behaviors illegal on the basis of the types that are thus assigned. For example, a type system may classify the value "hello" as a string and the value 5 as a number, and prohibit the programmer from adding "hello" to 5 based on that type assignment. In this type system, the program
"hello" + 5
would be illegal. Hence, any program permitted by the type system would be provably free from the erroneous behavior of adding strings and numbers.
The design and implementation of type systems is a topic nearly as broad as the topic of programming languages itself. In fact, type theory proponents commonly proclaim that the design of type systems is the very essence of programming language design: "Design the type system correctly, and the language will design itself."
Note that type theory, as described herein, refers to static typing disciplines. Programming systems and languages that employ dynamic typing do not prove a priori that a program uses values correctly; instead they raise an error at runtime, when the program attempts to perform some behavior that uses values incorrectly. Some claim that "dynamic typing" is a misnomer for this reason. However, in many dynamically typed, object-oriented languages, a type is more of an interface and as long as classes share common interfaces, one does not care of what class the object is. In any case, the two should not be confused.
Further reading
- Benjamin Pierce, Types and Programming Languages, MIT Press, 2002. (ISBN 0-262-16209-1)
- Glynn Winskel: The Formal Semantics of Programming Languages, An Introduction, The MIT Press 1993 (ISBN 0-262-23169-7)
- Luca Cardelli, "Type Systems," The Computer Science and Engineering Handbook, Allen B. Tucker (Ed.), chapter 103, pp. 2208-2236, CRC Press, Boca Raton, FL, 1997. (online) (http://citeseer.ist.psu.edu/cardelli97type.html)
See also
External links
- Abstract data type (http://www.nist.gov/dads/HTML/abstractDataType.html)
- A summary paper on the formal basis of ADTs, relationship to category theory, and list of good references (http://www.cs.ucsd.edu/users/goguen/ps/beatcs-adj.ps.gz). Pages 3-4 appear relevant. Reference number [6] looks good, but it may not be available online.
- Naïve Computational Type Theory (http://www.nuprl.org/documents/Constable/NaiveTypeTheoryPreface.html) by Robert L. Constablede:Typentheorie