This post is the first in a sequence of posts meant to be an introduction to pragmatic type theory. “Type theory” here refers to *Martin-Löf dependent type theory* (MLTT), as opposed to theories like the simply-typed lambda calculus; the main difference being that in MLTT, functions can also act on types and not just values, which makes it a more powerful theory.

I was initially motivated to study type theory because of a remark in the Alignment Research Field Guide about how defining terms and adding type annotations to them can make the topic of alignment research discussions more precise, as an intermediate step between vague idea and fully formalized proof.

You might also be aware that type theory can serve as an alternative foundation for mathematics, in place of set theory. And some people think type theory is the more elegant choice of the two; a point which this article is for example arguing for. Another reason to learn type theory is that it serves as the basis of most theorem provers.

I’m not aware of any short-ish but still pretty comprehensive introductions to MLTT, so that's why I wrote this sequence of posts. The content is mostly based on the book Homotopy Type Theory, with the main difference that the book tries to convince you to do *constructive* mathematics, whereas I won’t. (I also won’t talk about any homotopies at all.) This means though that if you’re interested in constructive mathematics (or homotopies), you should probably just read the book instead.

I will sometimes compare type concepts to concepts found in programming languages, but if you don’t have any programming experience, you can just ignore that. What you should have though, is a good understanding of *set theory*, because I will reference it frequently.

With that said, let’s get into it!

## Type judgments

A simple type annotation looks like this:

where is a type and is an element of this type. This looks very similar to the statement “” where is a set, and it *is* quite similar, but there are some important differences.

For one, types are usually stricter than sets when it comes to membership. In set theory, an object can easily be a member of multiple sets. In type theory, an object usually only belongs to a single type (though maybe that's not quite the case when union types are involved).

The other difference is that “” can be used as a proposition within a logic formula like this:

but you cannot do that in type theory. For example, something like “” doesn’t make any sense. Type judgements (i.e., the “” part) can only be applied from the outside to a full statement. For example, you could have some formula , describing the result of some computation, and then you can claim “” (formula is of type ) and that is then either true (more precisely, “well-typed”) or false (“not well-typed”) as seen from the outside. But type judgments cannot be used *inside* a statement as a true-or-false-valued term.

It’s like if you had a programming language that lacked any kind of type introspection, such that at runtime you couldn’t write an if-statement that branches based on the type of some object. But external programs like the compiler and static analysis tools identify the type, and tell us if we wrote our program correctly; for example, whether the values we are passing to functions have the appropriate type.

There is a caveat to the rule that something like “” may not appear within formulas and this concerns universal and existential quantification. Later, we will define these two quantifiers to write formulas like

but even here, “” is not something that can be true or false; it’s just an indicator for the “domain” of the quantifier.

So, membership in a type cannot be used as a proposition in type theory, but then how do we express things like “” where is, for example, some “subset” on the integers? The solution we’ll use is to define “subsets” as *predicates* (or *characteristic functions*) on some base type. So, you could, for example, define a set in via a predicate function, i.e., a function that takes in an and returns *true* or *false*. And then you could ask questions about membership in this “set” by just applying the predicate function. We will later see how this works in detail.

## Product types

Speaking of functions, how do we type-annotate those? Before we get there, let’s talk about something simpler first: pairs of values. If we have two values: and , then we can form a pair that has the type :

In contrast to (the usual definition of) set theory, type theory has *ordered pairs* as a native building block. The definition of ordered pairs goes along with a definition of projection functions (going from to, e.g., just ) but we’ll get there later.

For -tuples, we can pair repeatedly:

However, we usually leave out the extra parentheses:

while always implying that parentheses open after any “” and close at the very end of the expression.

Now, back to functions. If we have a function , one thing we can annotate is its return type. We could maybe do it like this:

However, we would also like to know the type of the argument , so that we can know what values we can pass to this function. Say that our function maps values from to . Type theorists have developed a brilliant notation for this:

Now, you might be saying: what the heck is this? And I’d agree with you, but there is some justification for writing a function type like this. You see, a function could be seen as a very long ordered tuple, where each entry of the tuple is associated with a particular input value. The entries of the tuple all have type , so the type of the tuple is kind of

with one entry for every value . Hence, we write it as a product: . In set theory, the set of all functions from to is written for a similar reason. (Why are we not writing it like that in type theory? We’ll see later how the is useful.)

In contrast to set theory, functions are a *fundamental* concept in type theory, and are not defined in terms of other things. There are three basic building blocks in type theory: values, functions, and types. (And then you can additionally construct *ordered pairs* out of any combination of these.) Values could also be seen as constant functions that don’t accept any arguments, so, in a sense there are only functions and types, but we will talk about “values” as separate things nevertheless.

The basic theory of functions that type theory is built on is lambda calculus. I will just quickly summarize it here. Feel free to skip this next section if you are already familiar.

## Aside on Lambda Calculus

Say you have a function like:

If you want to *apply* this function now to the number 4, then the rules of lambda calculus tell you to replace all ’s with “4”:

which probably doesn’t come as a surprise.

Now, in this example, was a *named function* (its name is “f”), but often it’s inconvenient to give every function a name, so we need a notation for *anonymous functions*. This is most useful when some function takes another function as an argument.

For example, the Fourier transform transforms functions and if we let the transform be denoted by then applying it to a function looks like this: . However, we might not always want to give the function passed to a name. In this case we can pass it an anonymous function. My preferred notation for anonymous functions is something like

where is mapped to . So that you can write for its Fourier transform. But the notation used in lambda calculus is this:

(and so we’ll be using this notation). The lambda () is not meant to be a variable here, but a marker that marks the beginning of a function. The variable that comes after the is the input argument and what comes after the dot () is the function body. Applying the Fourier transform to it looks like this: .

Anonymous functions (and named function too, actually) may only take a single argument, but as we’ll later see, we can get around this restriction by passing in -tuples as arguments or by using nested functions. I know this notation takes some getting used to, but it won’t feel strange after a while. As before, we’ll have the convention that the function body extends until the end of the expression (if there are no parentheses).

The following two are completely equivalent then:

(However, whenever possible, we will prefer the first notation.) Applying anonymous functions works exactly like named functions; all occurrences of the input argument are replaced and we can drop the part before the dot:

The variable following the is a temporary variable and the concrete letter used doesn’t matter. So the following two functions are completely identical:

Sometimes you have to be a bit careful in function application when there is a risk of a naming clash. This can happen when you have nested functions.^{[1]}

## Function types

The identity function on the integers has the following type:

Notice that functions are *instances* of some function type; a single function *type* can be associated with many different concrete functions.

Sometimes we also explicitly annotate the type of the input argument:

However, we usually only do this if the type is not fixed, as in the following example.

As it is, our identity function only works for one type: . But it would be nice if it worked for any type. We can achieve this by constructing a function that takes in a *type* as an additional argument, which in programming languages is known as a *generic function*. To do this, we need to talk about the type of types, so that we can specify the type of that additional argument.

The type of a type is called a universe . However, there can’t be a single universe that contains *all types* because then it would have to contain itself, which leads to problems like Russell’s paradox. So, instead, there will be an infinite hierarchy of type universes where each universe is contained in the next universe on the hierarchy: . Additionally, we’ll say this hierarchy is cumulative, so if then also . These detail doesn’t really matter to us though. What’s important to know is that for any type , there is some universe in the hierarchy of universes that contains this type: . As the exact universe is usually not important, we’ll usually drop the index .

With this knowledge, we can now define the generic identity function:

Let’s take a moment to understand this. We have nested functions: the outer function takes a type parameter and then returns the inner function, which is just the identity function, but on type (which we annotated explicitly). To get the identity function on the integers, you would do: , and then . For notational convenience, people often write the first type argument as a subscript:

In general, functions with more than one argument can be realized in two ways: either by modeling them as nested functions that each only take one argument (also called currying), or by modeling them as a single function that takes an ordered pair or -tuple as argument. However, we could not have realized the generic identity function using the latter method, because the type of the second argument depended on the value of the first argument. Currying is strictly more flexible than using tuples. Additionally, you always need projection functions when working with tuples. Speaking of which, here they are for an ordered pair:

The way we have defined these functions here is called function definition by *pattern matching*, because we have written the input argument in an *unpacked* form. The non-pattern-matching notation would have been , where is an ordered pair. However, with that notation we cannot express what this function does because… we haven’t defined any way to unpack a tuple yet; that’s what we’re trying to do right now! So, pattern matching is a very convenient way to describe new functionality that our theory didn’t have yet, even though it’s not technically legal in lambda calculus. (Don’t worry though, pattern matching can be defined rigorously; we just won’t do that here.) We will use pattern matching for later function definitions as well.

Just as a further example, here is the type of the add function on the reals, using currying:

We left out the parentheses in the type, as is customary. And here it is using pairs:

Multiplication has the same type, of course.

## Sum types

In the beginning I said that type theory has no *type introspection* that most programming languages have. But actually, through some cleverness, we can get something very similar. The setup is that we have some value , but we want to allow for it to be either of type or of type . The problem is that nothing within our theory can query the type. But we can solve this through *tagged unions*. Instead of a bare value , we’ll have a pair where the first element is a tag and the type of the second element depends on the value of the tag. This way, we can find out the type of simply by checking the value of the tag! (Assuming of course that we tagged everything correctly.)

You might think we could just use the pair type for this – like – but that’s not possible because we need the *type* of the second entry to depend on the *value* of the first entry. This can’t be done with what we already have, so we need to introduce a new type formation rule. And that is the *sum type*, also called *dependent pair type* (because it’s a pair where the type of the second entry is dependent on the first entry):

This means that is of type , and the type of is , which is a function with takes in and returns a *type* (so, it’s a type-valued function). Now, why is this written as a sum? It makes sense in a certain way: As we learned, the type of a pair is , which is kind of like a multiplication. But a multiplication is just repeated addition, so we could say

Thus, if we have an ordered pair where the second element depends on the value of the first, then the sum is a somewhat reasonable way to write this. The sum can also be seen as a *disjoint union* over the family of “sets” that is indexed by where the tag ensures that the “sets” are definitely disjoint. The resulting type can have elements from all the individual types .

In order to do anything with an instance of this tagged union, we need to handle all possible types that the second element of the pair can have. This means we can’t easily write down a projection function for the second element, because we don’t know what the return type will be.

So, instead of defining a projection function, we’ll define how some function could consume a tagged union. will need to accept two arguments: the tag and the actual value . The type has to be something like this:

where is simply an arbitrary return type of (which could be another product or sum type). We can now define the function which every sum type has its own version of; it takes in a return type , a function and an element of the sum type:

Note that we had to make generic in in order to make sure that the overall return type matches the return type of . Note also that this is another instance of function definition by *pattern matching*; we’re unpacking the pair in the input argument definition, which isn’t normally a legal operation.

If you only have a handful of types that you want to take the union over, the this whole setup can be a bit overkill. For that case, there is a simpler notation that doesn’t mention the tags explicitly. If and are types, then the following is also a type:

It’s called a binary sum type and the notation follows straightforwardly from the idea that we were taking a sum over types.

Even though you can’t see any explicit tags in this definition, they are still kind of there, because for example if then we do **not** have . The elements of are different from the elements of and . In order to turn an into an element of , we have to use a special function, one of which is associated with every binary sum type, and there is of course also one for . These “tagging functions” will get the names and :

You can see how they can turn an element of into an element of . In order to use one of the values of , you again need a way to handle both possibilities. So, say you have functions and which take an argument of type and respectively, but both return something of type :

Then we can use a function called to map an element of to the right function:

It’s a bit tricky to give the implementation of , because we don’t have explicit tags – we only have the tagging functions. This means, we can only describe from the outside how will work; if the element of was tagged with , then we execute , and if it was tagged with , then we execute :

The knowledge of whether an element of comes from or is never encoded anywhere *within the system*, but from the outside, we can choose the correct function definition to execute. We have to assert that this function exists, because it cannot be defined with the other building blocks that we have. This is again an instance of a function definition by pattern matching; the suitable definition can be found by pattern matching any value against and .

It’s important to state here that in practice, you would likely not use the function explicitly. Rather, you can just allude to the fact that it’s possible to do two different things depending on which original type an element of a union had. Like, you would say “let , if came from , do this; otherwise do that.”

## Examples

An example of a function that can be modeled as returning a union is *division* on the rational numbers, including 0. As we know, division by 0 is not defined, but you could return a special symbol when dividing by 0. So, let’s say is the type that only contains one element, for which we could use the symbol , and we return that symbol when dividing by 0. Then the function would have this type:

When dealing with the output of this function in your derivation, you could (sloppily) say: “If the output is some , then we do X next; otherwise we handle it with Y.”

An example of a use case for non-binary sum types is the definition of mathematical “data structures” like a ring or a group. These data structures are usually defined as a tuple, where the first element is a set, and the other elements are functions or other structures based on that set. In type theory, the set would be a type, obviously, but when we try to just define the data structure as a tuple, we will encounter the problem that the type of later tuple entries depends on the value of the first tuple entry.

To make this concrete, let’s consider groups. A group is a set with a binary operation, , and a neutral element, . So, groups should have this type:

A tuple of a type, a binary operation and an element of the type. However, how do we ensure that is actually the type given in the first entry of the tuple? Clearly, we need a sum type here; after all, a sum type is just a pair where the type of the second element depends on the value of the first element:

As usual, we left out the parentheses around the last two terms. This type of all groups is a union over all pairs of a binary operation and a neutral element, tagged with the type that they’re operating in. With this type, we could now write a function that takes in an arbitrary group, and it would know exactly what to do with it, because the “tag” (the first element of this 3-tuple) would tell the function what the underlying type is and what to expect with the binary operation and the neutral element.

Similarly, in set theory, an *ordered set* is technically a tuple of a set and an order relation. In type theory, we can analogously have a dependent pair (aka a sum type) of a type and an order relation on that type: where “” is a relation on . However, we haven’t discussed how to define relations yet.

This concludes the first part of this series. In the next post, we’ll learn how to define functions that return truth values, which includes predicate functions and relations.

*Thanks to Simon Fischer for comments on a draft of this post.*

^{^}For example, the following function returns another function that always returns a constant, which is set by the outer function:

So, for example, this returns a function that always returns 4:

It might be a little clearer if we write this with the other notation:

Now, the problem appears if we re-use one of the inner argument variables outside:

If we were just blindly following the substitution rule, we would get this:

which is of course not correct, because the result of a function application shouldn’t change just because we renamed some variables. To get the correct result, we need to avoid the naming clash by renaming the inner argument variable:

This introduction is fantastic. I don't think I've seen something as comprehensive, clear and short as this before.

Edit:

That said, I would have loved it if you introduced a few exercises throughout, or perhaps spoilered the types of some objects so people who are new to the area could guess things in advance. I remember a lot of things clicked for me when I set about trying to "discover" the type theory formalism myself.

I am also very happy about this; I learned something new, and the explanations felt perfectly clear.

Especially I liked the explanations "from outside perspective", like lambda notation vs arrow notation, or why the product symbol is used. These things are typically not mentioned in textbooks, because they teach the official notation, but this is exactly what you need as a beginner, to connect what you already know with the new things.

Cool! (Nitpick: You should probably mention that you are deviating from the naming in the HoTT book. AFAIK usually Π and Σ types are called Pi and Sigma types respectively, while the words "product" and "sum" (or "coproduct" in the HoTT book) are reserved for A×B and A+B.)

I am especially looking forward to discussion on how MLTT relates to alignment research and how it can be used for informal reasoning as Alignment Research Field Guide mentions.

I always get confused when the term "type signature" is used in text unrelated to type theory. Like what do people mean when they say things like "What’s the type signature of an agent?" or "the type of agency is (A→B)→A"?

Please don't defend the "∏" notation.

f:∏x:XYIt's nonsensical. It implies that

λ(x:N).xhas type " ∞! × 0"!

How so? It looks like you have confused ∏x:XY with ∏x:Xx. In this example we have X=Y=N, so the type of λ(x:N).x is ∏x:NN.

Pardon me. I guess its type is N∞.

I have recently read The Little Typer by Friedman and Christiansen. I suspect that this book can serve as an introduction similarly to this (planned, so far) sequence of posts. However, the book is not concise at all.