# Simply typed lambda calculus

The simply typed lambda calculus ($\lambda ^{\to }$ ), a form of type theory, is a typed interpretation of the lambda calculus with only one type constructor: $\to$ that builds function types. It is the canonical and simplest example of a typed lambda calculus. The simply typed lambda calculus was originally introduced by Alonzo Church in 1940 as an attempt to avoid paradoxical uses of the untyped lambda calculus, and it exhibits many desirable and interesting properties.

The term simple type is also used to refer to extensions of the simply typed lambda calculus such as products, coproducts or natural numbers (System T) or even full recursion (like PCF). In contrast, systems which introduce polymorphic types (like System F) or dependent types (like the Logical Framework) are not considered simply typed. The former are still considered simple because the Church encodings of such structures can be done using only $\to$ and suitable type variables, while polymorphism and dependency cannot.

## Syntax

To define the types, we begin by fixing a set of base types, $B$ . These are sometimes called atomic types or type constants. With this fixed, the syntax of types is:

$\tau ::=\tau \to \tau \mid T\quad \mathrm {where} \quad T\in B$ .

We also fix a set of term constants for the base types. For example, we might assume a base type nat, and the term constants could be the natural numbers. In the original presentation, Church used only two base types: $o$ for "the type of propositions" and $\iota$ for "the type of individuals". The type $o$ has no term constants, whereas $\iota$ has one term constant. Frequently the calculus with only one base type, usually $o$ , is considered.

The syntax of the simply typed lambda calculus is essentially that of the lambda calculus itself. We write $x{\mathbin {:}}\tau$ to denote that the variable $x$ is of type $\tau$ . The term syntax is then:

$e::=x\mid \lambda x{\mathbin {:}}\tau .e\mid e\,e\mid c$ That is, variable reference, abstractions, application, and constant. A variable reference $x$ is bound if it is inside of an abstraction binding $x$ . A term is closed if there are no unbound variables.

Compare this to the syntax of untyped lambda calculus:

$e::=x\mid \lambda x.e\mid e\,e$ We see that in typed lambda calculus every function (abstraction) must specify the type of its argument.

## Typing rules

To define the set of well typed lambda terms of a given type, we will define a typing relation between terms and types. First, we introduce typing contexts or typing environments $\Gamma ,\Delta ,\dots$ , which are sets of typing assumptions. A typing assumption has the form $x{\mathbin {:}}\sigma$ , meaning $x$ has type $\sigma$ .

The typing relation $\Gamma \vdash e{\mathbin {:}}\sigma$ indicates that $e$ is a term of type $\sigma$ in context $\Gamma$ . In this case $e$ is said to be well-typed (having type $\sigma$ )". Instances of the typing relation are called typing judgements. The validity of a typing judgement is shown by providing a typing derivation, constructed using typing rules (wherein the premises above the line allow us to derive the conclusion below the line). Simply-typed lambda calculus uses these rules:

In other words,

Examples of closed terms, i.e. terms typable in the empty context, are:

These are the typed lambda calculus representations of the basic combinators of combinatory logic.

$o(\iota \to \iota \to \iota )=1$ $o((\iota \to \iota )\to \iota )=2$ ## Semantics

### Intrinsic vs. extrinsic interpretations

Broadly speaking, there are two different ways of assigning meaning to the simply typed lambda calculus, as to typed languages more generally, sometimes called intrinsic vs. extrinsic, or Church-style vs. Curry-style. An intrinsic/Church-style semantics only assigns meaning to well-typed terms, or more precisely, assigns meaning directly to typing derivations. This has the effect that terms differing only by type annotations can nonetheless be assigned different meanings. For example, the identity term $\lambda x{\mathbin {:}}{\mathtt {int}}.~x$ on integers and the identity term $\lambda x{\mathbin {:}}{\mathtt {bool}}.~x$ on booleans may mean different things. (The classic intended interpretations are the identity function on integers and the identity function on boolean values.) In contrast, an extrinsic/Curry-style semantics assigns meaning to terms regardless of typing, as they would be interpreted in an untyped language. In this view, $\lambda x{\mathbin {:}}{\mathtt {int}}.~x$ and $\lambda x{\mathbin {:}}{\mathtt {bool}}.~x$ mean the same thing (i.e., the same thing as $\lambda x.~x$ ).

The distinction between intrinsic and extrinsic semantics is sometimes associated with the presence or absence of annotations on lambda abstractions, but strictly speaking this usage is imprecise. It is possible to define a Curry-style semantics on annotated terms simply by ignoring the types (i.e., through type erasure), as it is possible to give a Church-style semantics on unannotated terms when the types can be deduced from context (i.e., through type inference). The essential difference between intrinsic and extrinsic approaches is just whether the typing rules are viewed as defining the language, or as a formalism for verifying properties of a more primitive underlying language. Most of the different semantic interpretations discussed below can be seen through either Church or Curry goggles.

### Equational theory

The simply typed lambda calculus has the same equational theory of βη-equivalence as untyped lambda calculus, but subject to type restrictions. The equation for beta reduction

$(\lambda x{\mathbin {:}}\sigma .~t)\,u=_{\beta }t[x:=u]$ $\lambda x{\mathbin {:}}\sigma .~t\,x=_{\eta }t$ ### Operational semantics

Likewise, the operational semantics of simply typed lambda calculus can be fixed as for the untyped lambda calculus, using call by name, call by value, or other evaluation strategies. As for any typed language, type safety is a fundamental property of all of these evaluation strategies. Additionally, the strong normalization property described below implies that any evaluation strategy will terminate on all simply typed terms.

### Categorical semantics

The simply typed lambda calculus (with $\beta \eta$ -equivalence) is the internal language of Cartesian closed categories (CCCs), as was first observed by Lambek. Given any specific CCC, the basic types of the corresponding lambda calculus are just the objects, and the terms are the morphisms. Conversely, every simply typed lambda calculus gives a CCC whose objects are the types, and morphisms are equivalence classes of terms.

$\pi _{1}(s{\mathbin {:}}\sigma ,t{\mathbin {:}}\tau )=s{\mathbin {:}}\sigma$ $\pi _{2}(s{\mathbin {:}}\sigma ,t{\mathbin {:}}\tau )=t{\mathbin {:}}\tau$ $(\pi _{1}(u{\mathbin {:}}\sigma \times \tau ),\pi _{2}(u{\mathbin {:}}\sigma \times \tau ))=u{\mathbin {:}}\sigma \times \tau$ $t{\mathbin {:}}1=()$ This last is read as "if t has type 1, then it reduces to nil".

The above can then be turned into a category by taking the types as the objects. The morphisms $\sigma \to \tau$ are equivalence classes of pairs $(x{\mathbin {:}}\sigma ,t{\mathbin {:}}\tau )$ where x is a variable (of type $\sigma$ )and t is a term (of type $\tau$ ), having no free variables in it, except for (optionally) x. Closure is obtained from currying and application, as usual.

More precisely, there exist functors between the category of Cartesian closed categories, and the category of simply-typed lambda theories.

It is common to extend this case to closed symmetric monoidal categories by using a linear type system. The reason for this is that the CCC is a special case of the closed symmetric monoidal category, which is typically taken to be the category of sets. This is fine for laying the foundations of set theory, but the more general topos seems to provide a superior foundation.

### Proof-theoretic semantics

The simply typed lambda calculus is closely related to the implicational fragment of propositional intuitionistic logic, i.e., minimal logic, via the Curry–Howard isomorphism: terms correspond precisely to proofs in natural deduction, and inhabited types are exactly the tautologies of minimal logic.

## Alternative syntaxes

The presentation given above is not the only way of defining the syntax of the simply typed lambda calculus. One alternative is to remove type annotations entirely (so that the syntax is identical to the untyped lambda calculus), while ensuring that terms are well-typed via Hindley-Milner type inference. The inference algorithm is terminating, sound, and complete: whenever a term is typable, the algorithm computes its type. More precisely, it computes the term's principal type, since often an unannotated term (such as $\lambda x.~x$ ) may have more than one type (${\mathtt {int}}\to {\mathtt {int}}$ , ${\mathtt {bool}}\to {\mathtt {bool}}$ , etc., which are all instances of the principal type $\alpha \to \alpha$ ).

Another alternative presentation of simply typed lambda calculus is based on bidirectional type checking, which requires more type annotations than Hindley-Milner inference but is easier to describe. The type system is divided into two judgments, representing both checking and synthesis, written $\Gamma \vdash e\Leftarrow \tau$ and $\Gamma \vdash e\Rightarrow \tau$ respectively. Operationally, the three components $\Gamma$ , $e$ , and $\tau$ are all inputs to the checking judgment $\Gamma \vdash e\Leftarrow \tau$ , whereas the synthesis judgment $\Gamma \vdash e\Rightarrow \tau$ only takes $\Gamma$ and $e$ as inputs, producing the type $\tau$ as output. These judgments are derived via the following rules:

Observe that rules – are nearly identical to rules (1)–(4) above, except for the careful choice of checking or synthesis judgments. These choices can be explained like so:

Observe that the rules for synthesis are read top-to-bottom, whereas the rules for checking are read bottom-to-top. Note in particular that we do not need any annotation on the lambda abstraction in rule , because the type of the bound variable can be deduced from the type at which we check the function. Finally, we explain rules  and  as follows:

Because of these last two rules coercing between synthesis and checking, it is easy to see that any well-typed but unannotated term can be checked in the bidirectional system, so long as we insert "enough" type annotations. And in fact, annotations are needed only at β-redexes.

## General observations

Given the standard semantics, the simply typed lambda calculus is strongly normalizing: that is, well-typed terms always reduce to a value, i.e., a $\lambda$ abstraction. This is because recursion is not allowed by the typing rules: it is impossible to find types for fixed-point combinators and the looping term $\Omega =(\lambda x.~x~x)(\lambda x.~x~x)$ . Recursion can be added to the language by either having a special operator ${\mathtt {fix}}_{\alpha }$ of type $(\alpha \to \alpha )\to \alpha$ or adding general recursive types, though both eliminate strong normalization.

Since it is strongly normalising, it is decidable whether or not a simply typed lambda calculus program halts: in fact, it always halts. We can therefore conclude that the language is not Turing complete.