# GetWiki

*lambda calculus*

ARTICLE SUBJECTS

being →

database →

ethics →

fiction →

history →

internet →

language →

linux →

logic →

method →

news →

policy →

purpose →

religion →

science →

software →

truth →

unix →

wiki →

ARTICLE TYPES

essay →

feed →

help →

system →

wiki →

ARTICLE ORIGINS

critical →

forked →

imported →

original →

lambda calculus

[ temporary import ]

**please note:**

- the content below is remote from Wikipedia

- it has been imported raw for GetWiki

**Lambda calculus**(also written as

**Î»-calculus**) is a formal system in mathematical logic for expressing computation based on function abstraction and application using variable binding and substitution. It is a universal model of computation that can be used to simulate any Turing machine. It was first introduced by mathematician Alonzo Church in the 1930s as part of his research of the foundations of mathematics.Lambda calculus consists of constructing lambda terms and performing reduction operations on them. In the simplest form of lambda calculus, terms are built using only the following rules:{| class="wikitable"! Syntax !! Name !! Description

| A character or string representing a parameter or mathematical/logical value |

Free variables and bound variables>bound in the expression. |

| Applying a function to an argument. M and N are lambda terms. |

*x*.Î»

*y*.(Î»

*z*.(Î»

*x*.

*z x*) (Î»

*y.z y*)) (

*x y*)). Parentheses can be dropped if the expression is unambiguous. For some applications, terms for logical and mathematical constants and operations may be included.The reduction operations include:{| class="wikitable"! Operation !! Name !! Description

| Renaming the bound (formal) variables in the expression. Used to avoid name collisions. |

| Replacing the bound variable with the argument expression in the body of the abstraction |

## Explanation and applications

Lambda calculus is Turing complete, that is, it is a universal model of computation that can be used to simulate any Turing machine.JOURNAL, A. M., Turing, Alan Turing, Computability and Î»-Definability, 2268280, The Journal of Symbolic Logic, 2, 4, December 1937, 153â€“163, 10.2307/2268280, Its namesake, the Greek letter lambda (Î»), is used in**lambda expressions**and

**lambda terms**to denote binding a variable in a function.Lambda calculus may be

*untyped*or

*typed*. In typed lambda calculus, functions can be applied only if they are capable of accepting the given input's "type" of data. Typed lambda calculi are

*weaker*than the untyped lambda calculus, which is the primary subject of this article, in the sense that

*typed lambda calculi can express less*than the untyped calculus can, but on the other hand typed lambda calculi allow more things to be proved; in the simply typed lambda calculus it is, for example, a theorem that every evaluation strategy terminates for every simply typed lambda-term, whereas evaluation of untyped lambda-terms need not terminate. One reason there are many different typed lambda calculi has been the desire to do more (of what the untyped calculus can do) without giving up on being able to prove strong theorems about the calculus.Lambda calculus has applications in many different areas in mathematics, philosophy,Coquand, Thierry, "Type Theory",

*The Stanford Encyclopedia of Philosophy*(Summer 2013 Edition), Edward N. Zalta (ed.). linguistics,BOOK,weblink Categorial Investigations: Logical and Linguistic Aspects of the Lambek Calculus, Michael, Moortgat, Foris Publications, 1988, 9789067653879, {{Citation|url=https://books.google.com/books?id=nyFa5ngYThMC |title=Computing Meaning |editor1-first=Harry |editor1-last=Bunt |editor2-first=Reinhard |editor2-last=Muskens |publisher=Springer |year=2008 |isbn=9781402059575}} and computer science.{{citation|title=Concepts in Programming Languages|first=John C.|last=Mitchell|authorlink=John C. Mitchell|publisher=Cambridge University Press|year=2003|isbn=9780521780988|page=57|url=https://books.google.com/books?id=7Uh8XGfJbEIC&pg=PA57}}. Lambda calculus has played an important role in the development of the theory of programming languages. Functional programming languages implement the lambda calculus. Lambda calculus is also a current research topic in Category theory.BOOK, Basic Category Theory for Computer Scientists, 53, Benjamin C., Pierce, Benjamin C. Pierce,

## History

The lambda calculus was introduced by mathematician Alonzo Church in the 1930s as part of an investigation into the foundations of mathematics.JOURNAL, A., Church, Alonzo Church, A set of postulates for the foundation of logic, Annals of Mathematics, Series 2, 33, 2, 346â€“366, 1932, 10.2307/1968337, 1968337, For a full history, see Cardone and Hindley's "History of Lambda-calculus and Combinatory Logic" (2006). The original system was shown to be logically inconsistent in 1935 when Stephen Kleene and J. B. Rosser developed the Kleeneâ€“Rosser paradox.JOURNAL, Kleene, S. C., Stephen Kleene, Rosser, J. B., J. B. Rosser, The Inconsistency of Certain Formal Logics, The Annals of Mathematics, July 1935, 36, 3, 630, 10.2307/1968646, JOURNAL, Church, Alonzo, Alonzo Church, Review of Haskell B. Curry,*The Inconsistency of Certain Formal Logics*, The Journal of Symbolic Logic, December 1942, 7, 4, 170â€“171, 10.2307/2268117, 2268117, Subsequently, in 1936 Church isolated and published just the portion relevant to computation, what is now called the untyped lambda calculus.JOURNAL, A., Church, Alonzo Church, An unsolvable problem of elementary number theory, American Journal of Mathematics, 58, 2, 1936, 345â€“363, 10.2307/2371045, 2371045, In 1940, he also introduced a computationally weaker, but logically consistent system, known as the simply typed lambda calculus.JOURNAL, Church, Alonzo Church, A., 1940, A Formulation of the Simple Theory of Types, Journal of Symbolic Logic, 5, 2, 56â€“68, 10.2307/2266170, 2266170, Until the 1960s when its relation to programming languages was clarified, the Î»-calculus was only a formalism. Thanks to Richard Montague and other linguists' applications in the semantics of natural language, the Î»-calculus has begun to enjoy a respectable place in both linguisticsBOOK, Partee, B. B. H., ter Meulen, A., Wall, R. E., Mathematical Methods in Linguistics,weblink 29 Dec 2016, 1990, Springer, and computer science.Alama, Jesse "The Lambda Calculus",

*The Stanford Encyclopedia of Philosophy*(Summer 2013 Edition), Edward N. Zalta (ed.).

### Origin of the lambda symbol

There is a bit of controversy over the reason for Church's use of the Greek letter lambda ("Î»") as the notation for function-abstraction in the lambda calculus, perhaps in part due to conflicting explanations by Church himself. According to Cardone and Hindley (2006):By the way, why did Church choose the notation â€œÎ»â€? In [an unpublished 1964 letter to Harald Dickson] he stated clearly that it came from the notation â€œhat{x}â€ used for class-abstraction by Whitehead and Russell, by first modifying â€œhat{x}â€ to â€œâˆ§xâ€ to distinguish function-abstraction from class-abstraction, and then changing â€œâˆ§â€ to â€œÎ»â€ for ease of printing.This origin was also reported in [Rosser, 1984, p.338]. On the other hand, in his later years Church told two enquirers that the choice was more accidental: a symbol was needed and â€œÎ»â€ just happened to be chosen.Dana Scott has also addressed this controversy in various public lectures.Dana Scott, "Looking Backward; Looking Forward", Invited Talk at the Workshop in honour of Dana Scottâ€™s 85th birthday and 50 years of domain theory, 7-8 July, FLoC 2018 (talk 7 July 2018). The relevant passage begins at 32:50. (See also this extract of a May 2016 talk at the University of Birmingham, UK.)Scott recounts that he once posed a question about the origin of the lambda symbol to Church's son-in-law John Addison, who then wrote his father-in-law a postcard:Dear Professor Church,Russell had the iota operator, Hilbert had the epsilon operator. Why did you choose lambda for your operator?According to Scott, Church's entire response consisted of returning the postcard with the following annotation: "eeny, meeny, miny, moe".## Informal description

{{no footnotes|section|date=September 2013}}### Motivation

Computable functions are a fundamental concept within computer science and mathematics. The Î»-calculus provides a simple semantics for computation, enabling properties of computation to be studied formally. The Î»-calculus incorporates two simplifications that make this semantics simple.The first simplification is that the Î»-calculus treats functions "anonymously", without giving them explicit names. For example, the function
operatorname{square_sum}(x, y) = x^2 + y^2

can be rewritten in *anonymous form*as

(x, y) mapsto x^2 + y^2

(read as "a tuple of {{mvar|x}} and {{mvar|y}} is mapped to x^2 + y^2"). Similarly,
operatorname{id}(x) = x

can be rewritten in anonymous form as
x mapsto x

where the input is simply mapped to itself.The second simplification is that the Î»-calculus only uses functions of a single input. An ordinary function that requires two inputs, for instance the operatorname{square_sum} function, can be reworked into an equivalent function that accepts a single input, and as output returns *another*function, that in turn accepts a single input. For example,

(x, y) mapsto x^2 + y^2

can be reworked into
x mapsto (y mapsto x^2 + y^2)

This method, known as currying, transforms a function that takes multiple arguments into a chain of functions each with a single argument.Function application of the operatorname{square_sum} function to the arguments (5, 2), yields at once
((x, y) mapsto x^2 + y^2)(5, 2)
= 5^2 + 2^2
= 29,

whereas evaluation of the curried version requires one more step
Bigl(bigl(x mapsto (y mapsto x^2 + y^2)bigr)(5)Bigr)(2)
= (y mapsto 5^2 + y^2)(2) // the definition of x has been used with 5 in the inner expression. This is like Î²-reduction.
= 5^2 + 2^2 // the definition of y has been used with 2. Again, similar to Î²-reduction.
= 29

to arrive at the same result.### The lambda calculus

The lambda calculus consists of a language of**lambda terms**, which is defined by a certain formal syntax, and a set of transformation rules, which allow manipulation of the lambda terms. These transformation rules can be viewed as an equational theory or as an operational definition.As described above, all functions in the lambda calculus are anonymous functions, having no names. They only accept one input variable, with currying used to implement functions with several variables.

#### Lambda terms

The syntax of the lambda calculus defines some expressions as valid lambda calculus expressions and some as invalid, just as some strings of characters are valid C programs and some are not. A valid lambda calculus expression is called a "lambda term".The following three rules give an inductive definition that can be applied to build all syntactically valid lambda terms:- a variable, x, is itself a valid lambda term
- if t is a lambda term, and x is a variable, then (lambda x.t) is a lambda term (called a
**lambda abstraction**); - if t and s are lambda terms, then (ts) is a lambda term (called an
**application**).

*Notation*, below.A

**lambda abstraction**lambda x.t is a definition of an anonymous function that is capable of taking a single input x and substituting it into the expression t. It thus defines an anonymous function that takes x and returns t. For example, lambda x.x^2+2 is a lambda abstraction for the function f(x) = x^2 + 2 using the term x^2+2 for t. The definition of a function with a lambda abstraction merely "sets up" the function but does not invoke it. The abstraction binds the variable x in the term t.An

**application**ts represents the application of a function t to an input s, that is, it represents the act of calling function t on input s to produce t(s).There is no concept in lambda calculus of variable declaration. In a definition such as lambda x.x+y (i.e. f(x) = x + y), the lambda calculus treats y as a variable that is not yet defined. The lambda abstraction lambda x.x+y is syntactically valid, and represents a function that adds its input to the yet-unknown y.Bracketing may be used and may be needed to disambiguate terms. For example, lambda x.((lambda x.x)x) and (lambda x.(lambda x.x)) x denote different terms (although they coincidentally reduce to the same value). Here, the first example defines a function whose lambda term is the result of applying x to the child function, while the second example is the application of the outermost function to the input x, which returns the child function. Therefore, both examples evaluate to the identity function lambda x.x.

#### Functions that operate on functions

In lambda calculus, functions are taken to be 'first class values', so functions may be used as the inputs, or be returned as outputs from other functions.For example, lambda x.x represents the identity function, x mapsto x, and (lambda x.x)y represents the identity function applied to y. Further, (lambda x.y) represents the**constant function**x mapsto y, the function that always returns y, no matter the input. In lambda calculus, function application is regarded as left-associative, so that stx means (st)x.There are several notions of "equivalence" and "reduction" that allow lambda terms to be "reduced" to "equivalent" lambda terms.

#### Alpha equivalence

A basic form of equivalence, definable on lambda terms, is alpha equivalence. It captures the intuition that the particular choice of a bound variable, in a lambda abstraction, does not (usually) matter.For instance, lambda x.x and lambda y.y are alpha-equivalent lambda terms, and they both represent the same function (the identity function). The terms x and y are not alpha-equivalent, because they are not bound in a lambda abstraction.In many presentations, it is usual to identify alpha-equivalent lambda terms.The following definitions are necessary in order to be able to define beta reduction:#### Free variables

The**free variables**of a term are those variables not bound by a lambda abstraction. The set of free variables of an expression is defined inductively:

- The free variables of x are just x
- The set of free variables of lambda x.t is the set of free variables of t, but with x removed
- The set of free variables of ts is the union of the set of free variables of t and the set of free variables of s.

#### Capture-avoiding substitutions

Suppose t, s and r are lambda terms and x and y are variables.The notation t[x := r] indicates substitution of r for x in t in a*capture-avoiding*manner. This is defined so that:

- x[x := r] = r;
- y[x := r] = y if x neq y;
- (ts)[x := r] = (t[x := r])(s[x := r]);
- (lambda x.t)[x := r] = lambda x.t;
- (lambda y.t)[x := r] = lambda y.(t[x := r]) if x neq y and y is not in the free variables of r. The variable y is said to be "fresh" for r.

#### Beta reduction

The beta reduction rule states that an application of the form ( lambda x . t) s reduces to the term t [ x := s]. The notation ( lambda x . t ) s to t [ x := s ] is used to indicate that ( lambda x .t ) s beta reduces to t [ x := s ] .For example, for every s, ( lambda x . x ) s to x[ x := s ] = s . This demonstrates that lambda x . x really is the identity.Similarly, ( lambda x . y ) s to y [ x := s ] = y , which demonstrates that lambda x . y is a constant function.The lambda calculus may be seen as an idealised version of a functional programming language, like Haskell or Standard ML.Under this view, beta reduction corresponds to a computational step. This step can be repeated by additional beta conversions until there are no more applications left to reduce. In the untyped lambda calculus, as presented here, this reduction process may not terminate.For instance, consider the term Omega = (lambda x . xx)( lambda x . xx ).Here ( lambda x . xx)( lambda x . xx) to ( xx )[ x := lambda x . xx ] = ( x [ x := lambda x . xx ] )( x [ x := lambda x . xx ] ) = ( lambda x . xx)( lambda x . xx ).That is, the term reduces to itself in a single beta reduction, and therefore the reduction process will never terminate.Another aspect of the untyped lambda calculus is that it does not distinguish between different kinds of data.For instance, it may be desirable to write a function that only operates on numbers. However, in the untyped lambda calculus, there is no way to prevent a function from being applied to truth values, strings, or other non-number objects.## Formal definition

### Definition

Lambda expressions are composed of:- variables v1, v2, ..., vn, ...
- the abstraction symbols lambda 'Î»' and dot '.'
- parentheses ( )

- If x is a variable, then x âˆˆ Î›
- If x is a variable and M âˆˆ Î›, then (Î»x.M) âˆˆ Î›
- If M, N âˆˆ Î›, then (M N) âˆˆ Î›

|last=Barendregt

|first=Hendrik Pieter

|author-link=Henk Barendregt

|last2=

|first2=

|author2-link=

|title=The Lambda Calculus: Its Syntax and Semantics

|place=

|publisher=North Holland, Amsterdam

|year=1984

|volume=103

|series=Studies in Logic and the Foundations of Mathematics

|edition=Revised

|url=http://www.elsevier.com/wps/find/bookdescription.cws_home/501727/description

|doi=

|id=

|isbn=0-444-87508-5

|deadurl=yes

|archiveurl=https://web.archive.org/web/20040823174002weblink

|archivedate=2004-08-23

|df=

}} Corrections.|first=Hendrik Pieter

|author-link=Henk Barendregt

|last2=

|first2=

|author2-link=

|title=The Lambda Calculus: Its Syntax and Semantics

|place=

|publisher=North Holland, Amsterdam

|year=1984

|volume=103

|series=Studies in Logic and the Foundations of Mathematics

|edition=Revised

|url=http://www.elsevier.com/wps/find/bookdescription.cws_home/501727/description

|doi=

|id=

|isbn=0-444-87508-5

|deadurl=yes

|archiveurl=https://web.archive.org/web/20040823174002weblink

|archivedate=2004-08-23

|df=

### Notation

To keep the notation of lambda expressions uncluttered, the following conventions are usually applied:- Outermost parentheses are dropped: M N instead of (M N)
- Applications are assumed to be left associative: M N P may be written instead of ((M N) P)WEB,weblink Example for Rules of Associativity, Lambda-bound.com, 2012-06-18,
- The body of an abstraction extends as far right as possible: Î»x.M N means Î»x.(M N) and not (Î»x.M) N
- A sequence of abstractions is contracted: Î»x.Î»y.Î»z.N is abbreviated as Î»xyz.N

| first = Peter

| last = Selinger

| author-link =

| title = Lecture Notes on the Lambda Calculus

| year =2008

| page = 9

| place =

| publisher = Department of Mathematics and Statistics, University of Ottawa

| url =weblink

| bibcode = 2008arXiv0804.3434S

| volume = 0804

| arxiv = 0804.3434

| issue=class: cs.LO }}

| last = Selinger

| author-link =

| title = Lecture Notes on the Lambda Calculus

| year =2008

| page = 9

| place =

| publisher = Department of Mathematics and Statistics, University of Ottawa

| url =weblink

| bibcode = 2008arXiv0804.3434S

| volume = 0804

| arxiv = 0804.3434

| issue=class: cs.LO }}

### Free and bound variables

The abstraction operator, Î», is said to bind its variable wherever it occurs in the body of the abstraction. Variables that fall within the scope of an abstraction are said to be*bound*. In an expression Î»

*x*.

*M*, the part Î»

*x*is often called

*binder*, as a hint that the variable

*x*is getting bound by appending Î»

*x*to

*M*. All other variables are called

*free*. For example, in the expression Î»

*y*.

*x*

*x*

*y*, y is a bound variable and x is free. Also note that a variable is bound by its "nearest" abstraction. In the following example the single occurrence of x in the expression is bound by the second lambda: Î»

*x*.

*y*(Î»

*x*.

*z*

*x*)The set of

*free variables*of a lambda expression, M, is denoted as FV(M) and is defined by recursion on the structure of the terms, as follows:

- FV(x) = {x}, where x is a variable
- FV(Î»x.M) = FV(M) {x}
- FV(M N) = FV(M) âˆª FV(N){{Citation

| last = Barendregt

| first = Henk

| author-link = Henk Barendregt

| last2 = Barendsen

| first2 = Erik

| author2-link =

| title = Introduction to Lambda Calculus

| place =

| publisher =

| year = March 2000

| volume =

| edition =

| url =weblink

| doi =

| id =

| isbn = }}

An expression that contains no free variables is said to be | first = Henk

| author-link = Henk Barendregt

| last2 = Barendsen

| first2 = Erik

| author2-link =

| title = Introduction to Lambda Calculus

| place =

| publisher =

| year = March 2000

| volume =

| edition =

| url =weblink

| doi =

| id =

| isbn = }}

*closed*. Closed lambda expressions are also known as combinators and are equivalent to terms in combinatory logic.

## Reduction

The meaning of lambda expressions is defined by how expressions can be reduced.JOURNAL, Ruy de Queiroz, de Queiroz, Ruy J. G. B., 10.1111/j.1746-8361.1988.tb00919.x, A Proof-Theoretic Account of Programming and the Role of Reduction Rules, Dialectica, 42, 4, 265â€“282, 1988, There are three kinds of reduction:-
**Î±-conversion**: changing bound variables (**alpha**); -
**Î²-reduction**: applying functions to their arguments (**beta**); -
**Î·-conversion**: which captures a notion of extensionality (**eta**).

*Î²-equivalent*, if they can be Î²-converted into the same expression, and Î±/Î·-equivalence are defined similarly.The term

*redex*, short for

*reducible expression*, refers to subterms that can be reduced by one of the reduction rules. For example, (Î»

*x*.M) N is a beta-redex in expressing the substitution of N for x in M. The expression to which a redex reduces is called its reduct; the reduct of (Î»

*x*.M) N is M[

*x*:=N].If

*x*is not free in M, Î»

*x*.M

*x*is also an eta-redex, with a reduct of M.

### Î±-conversion

Alpha-conversion, sometimes known as alpha-renaming,{{Citation |title=Design concepts in programming languages |last1=Turbak |first1=Franklyn |last2=Gifford |first2=David |year=2008 |publisher=MIT press |page=251| isbn=978-0-262-20175-9}} allows bound variable names to be changed. For example, alpha-conversion of Î»*x*.

*x*might yield Î»

*y*.

*y*. Terms that differ only by alpha-conversion are called

*Î±-equivalent*. Frequently, in uses of lambda calculus, Î±-equivalent terms are considered to be equivalent.The precise rules for alpha-conversion are not completely trivial. First, when alpha-converting an abstraction, the only variable occurrences that are renamed are those that are bound to the same abstraction. For example, an alpha-conversion of Î»

*x*.Î»

*x*.

*x*could result in Î»

*y*.Î»

*x*.

*x*, but it could

*not*result in Î»

*y*.Î»

*x*.

*y*. The latter has a different meaning from the original. This is analogous to the programming notion of variable shadowing.Second, alpha-conversion is not possible if it would result in a variable getting captured by a different abstraction. For example, if we replace

*x*with

*y*in Î»

*x*.Î»

*y*.

*x*, we get Î»

*y*.Î»

*y*.

*y*, which is not at all the same.In programming languages with static scope, alpha-conversion can be used to make name resolution simpler by ensuring that no variable name masks a name in a containing scope (see alpha renaming to make name resolution trivial).In the De Bruijn index notation, any two alpha-equivalent terms are syntactically identical.

#### Substitution

Substitution, written {{mono|1=*E*[

*V*:=

*R*]}}, is the process of replacing all free occurrences of the variable {{mono|

*V*}} in the expression {{mono|

*E*}} with expression {{mono|

*R*}}.Substitution on terms of the Î»-calculus is defined by recursion on the structure of terms, as follows (note: x and y are only variables while M and N are any Î» expression).

*x*[

*x*:= N] ≡ N

*y*[

*x*:= N] ≡

*y*, if

*x*â‰

*y*

(M1 M2)[

*x*:= N] ≡ (M1[

*x*:= N]) (M2[

*x*:= N])

(Î»

*x*.M)[

*x*:= N] ≡ Î»

*x*.M

(Î»

*y*.M)[

*x*:= N] ≡ Î»

*y*.(M[

*x*:= N]), if

*x*â‰

*y*,

*provided*

*y*âˆ‰ FV(N)

*x*.

*y*)[

*y*:=

*x*]}} to result in {{mono|(Î»

*x*.

*x*)}}, because the substituted {{mono|

*x*}} was supposed to be free but ended up being bound. The correct substitution in this case is {{mono|(Î»

*z*.

*x*)}}, up to Î±-equivalence. Notice that substitution is defined uniquely up to Î±-equivalence.

### β-reduction

Beta-reduction captures the idea of function application. Beta-reduction is defined in terms of substitution: the beta-reduction of ((Î»*V*.

*E*)

*E′*) is

*E*[

*V*:=

*E′*].For example, assuming some encoding of 2, 7, ×, we have the following Î²-reduction: ((Î»

*n*.

*n*×2) 7) â†’ 7×2. Beta reduction can be seen to be the same as the concept of

*local reducibility*in natural deduction, via the Curryâ€“Howard isomorphism.

### η-conversion

Eta-conversion expresses the idea of extensionality, which in this context is that two functions are the same if and only if they give the same result for all arguments. Eta-conversion converts between Î»*x*.(

*f*

*x*) and

*f*whenever

*x*does not appear free in

*f*.Eta conversion can be seen to be the same as the concept of

*local completeness*in natural deduction, via the Curryâ€“Howard isomorphism.

## Normal forms and confluence

For the untyped lambda calculus, Î²-reduction as a rewriting rule is neither strongly normalising nor weakly normalising.However, it can be shown that Î²-reduction is confluent when working up to Î±-conversion (i.e. we consider two normal forms to be equal if it is possible to Î±-convert one into the other).Therefore, both strongly normalising terms and weakly normalising terms have a unique normal form. For strongly normalising terms, any reduction strategy is guaranteed to yield the normal form, whereas for weakly normalising terms, some reduction strategies may fail to find it.## Encoding datatypes

The basic lambda calculus may be used to model booleans, arithmetic, data structures and recursion, as illustrated in the following sub-sections.### Arithmetic in lambda calculus

There are several possible ways to define the natural numbers in lambda calculus, but by far the most common are the Church numerals, which can be defined as follows:
0 := Î»

and so on. Or using the alternative syntax presented above in *f*.Î»*x*.*x*1 := Î»*f*.Î»*x*.*f**x*2 := Î»*f*.Î»*x*.*f*(*f**x*) 3 := Î»*f*.Î»*x*.*f*(*f*(*f**x*))*Notation*:

0 := Î»

A Church numeral is a higher-order functionâ€”it takes a single-argument function *fx*.*x*1 := Î»*fx*.*f**x*2 := Î»*fx*.*f*(*f**x*) 3 := Î»*fx*.*f*(*f*(*f**x*))*f*, and returns another single-argument function. The Church numeral

*n*is a function that takes a function

*f*as argument and returns the

*n*-th composition of

*f*, i.e. the function

*f*composed with itself

*n*times. This is denoted

*f*(

*n*) and is in fact the

*n*-th power of

*f*(considered as an operator);

*f*(0) is defined to be the identity function. Such repeated compositions (of a single function

*f*) obey the laws of exponents, which is why these numerals can be used for arithmetic. (In Church's original lambda calculus, the formal parameter of a lambda expression was required to occur at least once in the function body, which made the above definition of 0 impossible.)One way of thinking about the Church numeral

*n*, which is often useful when analysing programs, is as an instruction 'repeat

*n*times'. For example, using the PAIR and NIL functions defined below, one can define a function that constructs a (linked) list of

*n*elements all equal to

*x*by repeating 'prepend another

*x*element'

*n*times, starting from an empty list. The lambda term is

Î»

By varying what is being repeated, and varying what argument that function being repeated is applied to, a great many different effects can be achieved.We can define a successor function, which takes a Church numeral *n*.Î»*x*.*n*(PAIR*x*) NIL*n*and returns

*n*+ 1 by adding another application of

*f*, where '(mf)x' means the function 'f' is applied 'm' times on 'x':

SUCC := Î»

Because the *n*.Î»*f*.Î»*x*.*f*(*n**f**x*)*m*-th composition of

*f*composed with the

*n*-th composition of

*f*gives the

*m*+

*n*-th composition of

*f*, addition can be defined as follows:

PLUS := Î»

PLUS can be thought of as a function taking two natural numbers as arguments and returning a natural number; it can be verified that
*m*.Î»*n*.Î»*f*.Î»*x*.*m**f*(*n**f**x*)
PLUS 2 3

and
5

are Î²-equivalent lambda expressions. Since adding *m*to a number

*n*can be accomplished by adding 1

*m*times, an alternative definition is:

PLUS := Î»

*m*.Î»*n*.*m*SUCC*n*{{Citation
| last1 = Felleisen

| first1 = Matthias

| last2 = Flatt

| first2 = Matthew

| authorlink =

| title = Programming Languages and Lambda Calculi

| publisher =

| year = 2006

| location =

| page = 26

| url =weblink

| archive-url =weblink" title="web.archive.org/web/20090205113235weblink">weblink

| archive-date = 2009-02-05

| doi =

| id =

| isbn = }}; a note (accessed 2017) at the original location suggests that the authors consider the work originally referenced to have been superseded by a book.

Similarly, multiplication can be defined as
| first1 = Matthias

| last2 = Flatt

| first2 = Matthew

| authorlink =

| title = Programming Languages and Lambda Calculi

| publisher =

| year = 2006

| location =

| page = 26

| url =weblink

| archive-url =weblink" title="web.archive.org/web/20090205113235weblink">weblink

| archive-date = 2009-02-05

| doi =

| id =

| isbn = }}; a note (accessed 2017) at the original location suggests that the authors consider the work originally referenced to have been superseded by a book.

MULT := Î»

Alternatively
*m*.Î»*n*.Î»*f*.*m*(*n**f*)
MULT := Î»

since multiplying *m*.Î»*n*.*m*(PLUS*n*) 0*m*and

*n*is the same as repeating the add

*n*function

*m*times and then applying it to zero.Exponentiation has a rather simple rendering in Church numerals, namely

POW := Î»

The predecessor function defined by PRED *b*.Î»*e*.*e**b**n*=

*n*âˆ’ 1 for a positive integer

*n*and PRED 0 = 0 is considerably more difficult. The formula

PRED := Î»

can be validated by showing inductively that if *n*.Î»*f*.Î»*x*.*n*(Î»*g*.Î»*h*.*h*(*g**f*)) (Î»*u*.*x*) (Î»*u*.*u*)*T*denotes (Î»

*g*.Î»

*h*.

*h*(

*g*

*f*)), then T(

*n*)(Î»

*u*.

*x*) = (Î»

*h*.

*h*(

*f*(

*n*âˆ’1)(

*x*))) for

*n*> 0. Two other definitions of PRED are given below, one using conditionals and the other using pairs. With the predecessor function, subtraction is straightforward. Defining

SUB := Î»

SUB *m*.Î»*n*.*n*PRED*m*,*m*

*n*yields

*m*âˆ’

*n*when

*m*>

*n*and 0 otherwise.

### Logic and predicates

By convention, the following two definitions (known as Church booleans) are used for the boolean values TRUE and FALSE:
TRUE := Î»

Then, with these two Î»-terms, we can define some logic operators (these are just possible formulations; other expressions are equally correct):
*x*.Î»*y*.*x*FALSE := Î»*x*.Î»*y*.*y*
(Note that FALSE is equivalent to the Church numeral zero defined above)

AND := Î»

We are now able to compute some logic functions, for example:
*p*.Î»*q*.*p**q**p*OR := Î»*p*.Î»*q*.*p**p**q*NOT := Î»*p*.p FALSE TRUE IFTHENELSE := Î»*p*.Î»*a*.Î»*b*.*p**a**b*
AND TRUE FALSE

and we see that AND TRUE FALSE is equivalent to FALSE.A
â‰¡ (Î»

*p*.Î»*q*.*p**q**p*) TRUE FALSE â†’Î² TRUE FALSE TRUE â‰¡ (Î»*x*.Î»*y*.*x*) FALSE TRUE â†’Î² FALSE*predicate*is a function that returns a boolean value. The most fundamental predicate is ISZERO, which returns TRUE if its argument is the Church numeral 0, and FALSE if its argument is any other Church numeral:

ISZERO := Î»

The following predicate tests whether the first argument is less-than-or-equal-to the second:
*n*.*n*(Î»*x*.FALSE) TRUE
LEQ := Î»

and since *m*.Î»*n*.ISZERO (SUB*m**n*),*m*=

*n*, if LEQ

*m*

*n*and LEQ

*n*

*m*, it is straightforward to build a predicate for numerical equality.The availability of predicates and the above definition of TRUE and FALSE make it convenient to write "if-then-else" expressions in lambda calculus. For example, the predecessor function can be defined as:

PRED := Î»

which can be verified by showing inductively that *n*.*n*(Î»*g*.Î»*k*.ISZERO (*g*1)*k*(PLUS (*g**k*) 1)) (Î»*v*.0) 0*n*(Î»

*g*.Î»

*k*.ISZERO (

*g*1)

*k*(PLUS (

*g*

*k*) 1)) (Î»

*v*.0) is the add

*n*âˆ’ 1 function for

*n*> 0.

### Pairs

A pair (2-tuple) can be defined in terms of TRUE and FALSE, by using the Church encoding for pairs. For example, PAIR encapsulates the pair (*x*,

*y*), FIRST returns the first element of the pair, and SECOND returns the second.

PAIR := Î»

A linked list can be defined as either NIL for the empty list, or the PAIR of an element and a smaller list. The predicate NULL tests for the value NIL. (Alternatively, with NIL := FALSE, the construct *x*.Î»*y*.Î»*f*.*f**x**y*FIRST := Î»*p*.*p*TRUE SECOND := Î»*p*.*p*FALSE NIL := Î»*x*.TRUE NULL := Î»*p*.*p*(Î»*x*.Î»*y*.FALSE)*l*(Î»

*h*.Î»

*t*.Î»

*z*.deal_with_head_

*h*_and_tail_

*t*) (deal_with_nil) obviates the need for an explicit NULL test).As an example of the use of pairs, the shift-and-increment function that maps (

*m*,

*n*) to (

*n*,

*n*+ 1) can be defined as

Î¦ := Î»

which allows us to give perhaps the most transparent version of the predecessor function:
*x*.PAIR (SECOND*x*) (SUCC (SECOND*x*))
PRED := Î»

*n*.FIRST (*n*Î¦ (PAIR 0 0)).## Additional programming techniques

There is a considerable body of programming idioms for lambda calculus. Many of these were originally developed in the context of using lambda calculus as a foundation for programming language semantics, effectively using lambda calculus as a low-level programming language. Because several programming languages include the lambda calculus (or something very similar) as a fragment, these techniques also see use in practical programming, but may then be perceived as obscure or foreign.### Named constants

In lambda calculus, a library would take the form of a collection of previously defined functions, which as lambda-terms are merely particular constants. The pure lambda calculus does not have a concept of named constants since all atomic lambda-terms are variables, but one can emulate having named constants by setting aside a variable as the name of the constant, using lambda-abstraction to bind that variable in the main body, and apply that lambda-abstraction to the intended definition. Thus to use*f*to mean

*M*(some explicit lambda-term) in

*N*(another lambda-term, the "main program"), one can say

(Î»

Authors often introduce syntactic sugar, such as let, to permit writing the above in the more intuitive order
*f*.*N*)*M*
let

By chaining such definitions, one can write a lambda calculus "program" as zero or more function definitions, followed by one lambda-term using those functions that constitutes the main body of the program.A notable restriction of this let is that the name *f*=*M*in*N**f*is not defined in

*M*, since

*M*is outside the scope of the lambda-abstraction binding

*f*; this means a recursive function definition cannot be used as the

*M*with let. The more advanced letrec syntactic sugar construction that allows writing recursive function definitions in that naive style instead additionally employs fixed-point combinators.

### Recursion and fixed points

{{see also|SKI combinator calculus#Self-application and recursion}}Recursion is the definition of a function using the function itself. Lambda calculus cannot express this as directly as some other notations: all functions are anonymous in lambda calculus, so we can't refer to a value which is yet to be defined, inside the lambda term defining that same value. However, recursion can still be achieved by arranging for a lambda expression to receive itself as its argument value, for example in (Î»*x*.

*x*

*x*)

*E*.Consider the factorial function F(

*n*) recursively defined by

F(

In the lambda expression which is to represent this function, a *n*) = 1, if*n*= 0; else*n*× F(*n*âˆ’ 1).*parameter*(typically the first one) will be assumed to receive the lambda expression itself as its value, so that calling it – applying it to an argument – will amount to recursion. Thus to achieve recursion, the intended-as-self-referencing argument (called

*r*here) must always be passed to itself within the function body, at a call point:

G := Î»
F := G G = (Î»

The self-application achieves replication here, passing the function's lambda expression on to the next invocation as an argument value, making it available to be referenced and called there.This solves it but requires re-writing each recursive call as self-application. We would like to have a generic solution, without a need for any re-writes:
*r*. Î»*n*.(1, if*n*= 0; else*n*× (*r**r*(*n*âˆ’1)))
with

*r**r**x*= F*x*= G*r**x*to hold, so*r*= G and*x*.*x**x*) G
G := Î»
F := FIX G where FIX

Given a lambda term with first argument representing recursive call (e.g. G here), the *r*. Î»*n*.(1, if*n*= 0; else*n*× (*r*(*n*âˆ’1)))
with

*r**x*= F*x*= G*r**x*to hold, so*r*= G*r*=: FIX G and*g*:= (*r*where*r*=*g**r*) =*g*(FIX*g*)
so that FIX G = G (FIX G) = (Î»

*n*.(1, if*n*= 0; else*n*× ((FIX G) (*n*âˆ’1))))*fixed-point*combinator FIX will return a self-replicating lambda expression representing the recursive function (here, F). The function does not need to be explicitly passed to itself at any point, for the self-replication is arranged in advance, when it is created, to be done each time it is called. Thus the original lambda expression (FIX G) is re-created inside itself, at call-point, achieving self-reference.In fact, there are many possible definitions for this FIX operator, the simplest of them being:

**Y**:= Î»

*g*.(Î»

*x*.

*g*(

*x*

*x*)) (Î»

*x*.

*g*(

*x*

*x*))

**Y**

*g*is a fixed-point of

*g*, as it expands to:

**Y**

*g*(Î»

*h*.(Î»

*x*.

*h*(

*x*

*x*)) (Î»

*x*.

*h*(

*x*

*x*)))

*g*(Î»

*x*.

*g*(

*x*

*x*)) (Î»

*x*.

*g*(

*x*

*x*))

*g*((Î»

*x*.

*g*(

*x*

*x*)) (Î»

*x*.

*g*(

*x*

*x*)))

*g*(

**Y**

*g*)

**Y**G)

*n*, where

*n*is the number we are calculating the factorial of. Given

*n*= 4, for example, this gives:

(

Every recursively defined function can be seen as a fixed point of some suitably defined function closing over the recursive call with an extra argument, and therefore, using **Y**G) 4 G (**Y**G) 4 (Î»*r*.Î»*n*.(1, if*n*= 0; else*n*Ã— (*r*(*n*âˆ’1)))) (**Y**G) 4 (Î»*n*.(1, if*n*= 0; else*n*Ã— ((**Y**G) (*n*âˆ’1)))) 4 1, if 4 = 0; else 4 Ã— ((**Y**G) (4âˆ’1)) 4 Ã— (G (**Y**G) (4âˆ’1)) 4 Ã— ((Î»*n*.(1, if*n*= 0; else*n*Ã— ((**Y**G) (*n*âˆ’1)))) (4âˆ’1)) 4 Ã— (1, if 3 = 0; else 3 Ã— ((**Y**G) (3âˆ’1))) 4 Ã— (3 Ã— (G (**Y**G) (3âˆ’1))) 4 Ã— (3 Ã— ((Î»*n*.(1, if*n*= 0; else*n*Ã— ((**Y**G) (*n*âˆ’1)))) (3âˆ’1))) 4 Ã— (3 Ã— (1, if 2 = 0; else 2 Ã— ((**Y**G) (2âˆ’1)))) 4 Ã— (3 Ã— (2 Ã— (G (**Y**G) (2âˆ’1)))) 4 Ã— (3 Ã— (2 Ã— ((Î»*n*.(1, if*n*= 0; else*n*Ã— ((**Y**G) (*n*âˆ’1)))) (2âˆ’1)))) 4 Ã— (3 Ã— (2 Ã— (1, if 1 = 0; else 1 Ã— ((**Y**G) (1âˆ’1))))) 4 Ã— (3 Ã— (2 Ã— (1 Ã— (G (**Y**G) (1âˆ’1))))) 4 Ã— (3 Ã— (2 Ã— (1 Ã— ((Î»*n*.(1, if*n*= 0; else*n*Ã— ((**Y**G) (*n*âˆ’1)))) (1âˆ’1))))) 4 Ã— (3 Ã— (2 Ã— (1 Ã— (1, if 0 = 0; else 0 Ã— ((**Y**G) (0âˆ’1)))))) 4 Ã— (3 Ã— (2 Ã— (1 Ã— (1)))) 24**Y**, every recursively defined function can be expressed as a lambda expression. In particular, we can now cleanly define the subtraction, multiplication and comparison predicate of natural numbers recursively.

### Standard terms

Certain terms have commonly accepted names:
{{anchor|I}}

Several of these have direct applications in the **I**:= Î»*x*.*x*{{anchor|K}}**K**:= Î»*x*.Î»*y*.*x*{{anchor|S}}**S**:= Î»*x*.Î»*y*.Î»*z*.*x**z*(*y**z*) {{anchor|B}}**B**:= Î»*x*.Î»*y*.Î»*z*.*x*(*y**z*) {{anchor|C}}**C**:= Î»*x*.Î»*y*.Î»*z*.*x**z**y*{{anchor|W}}**W**:= Î»*x*.Î»*y*.*x**y**y*{{anchor|U}}**U**:= Î»*x*.*x**x*{{anchor|omega}}**Ï‰**:= Î»*x*.*x**x*{{anchor|Omega}}**Î©**:=**Ï‰ Ï‰**{{anchor|Y}}**Y**:= Î»*g*.(Î»*x*.*g*(*x**x*)) (Î»*x*.*g*(*x**x*))*elimination of lambda-abstraction*that turns lambda terms into combinator calculus terms.

### Abstraction elimination

If*N*is a lambda-term without lambda-abstraction, but possibly containing named constants (combinators), then there exists a lambda-term

*T*(

*x*,

*N*) which is equivalent to Î»

*x*.

*N*but lacks lambda-abstraction (except as part of the named constants, if these are considered non-atomic). This can also be viewed as anonymising variables, as

*T*(

*x*,

*N*) removes all occurrences of

*x*from

*N*, while still allowing argument values to be substituted into the positions where

*N*contains an

*x*. The conversion function

*T*can be defined by:

*T*(

*x*,

*x*) :=

**I**

*T*(

*x*,

*N*) :=

**K**

*N*if

*x*is not free in

*N*.

*T*(

*x*,

*M*

*N*) :=

**S**

*T*(

*x*,

*M*)

*T*(

*x*,

*N*)

*T*(

*x*,

*N*)

*P*can reduce by having the initial combinator

**I**,

**K**, or

**S**grab the argument

*P*, just like Î²-reduction of (Î»

*x*.

*N*)

*P*would do.

**I**returns that argument.

**K**throws the argument away, just like (Î»

*x*.

*N*) would do if

*x*has no free occurrence in

*N*.

**S**passes the argument on to both subterms of the application, and then applies the result of the first to the result of the second.The combinators

**B**and

**C**are similar to

**S**, but pass the argument on to only one subterm of an application (

**B**to the "argument" subterm and

**C**to the "function" subterm), thus saving a subsequent

**K**if there is no occurrence of

*x*in one subterm. In comparison to

**B**and

**C**, the

**S**combinator actually conflates two functionalities: rearranging arguments, and duplicating an argument so that it may be used in two places. The

**W**combinator does only the latter, yielding the B, C, K, W system as an alternative to SKI combinator calculus.

## Typed lambda calculus

A**typed lambda calculus**is a typed formalism that uses the lambda-symbol (lambda) to denote anonymous function abstraction. In this context, types are usually objects of a syntactic nature that are assigned to lambda terms; the exact nature of a type depends on the calculus considered (see kinds below). From a certain point of view, typed lambda calculi can be seen as refinements of the untyped lambda calculus but from another point of view, they can also be considered the more fundamental theory and

*untyped lambda calculus*a special case with only one type.Types and Programming Languages, p. 273, Benjamin C. PierceTyped lambda calculi are foundational programming languages and are the base of typed functional programming languages such as ML and Haskell and, more indirectly, typed imperative programming languages. Typed lambda calculi play an important role in the design of type systems for programming languages; here typability usually captures desirable properties of the program, e.g. the program will not cause a memory access violation.Typed lambda calculi are closely related to mathematical logic and proof theory via the Curryâ€“Howard isomorphism and they can be considered as the internal language of classes of categories, e.g. the simply typed lambda calculus is the language of Cartesian closed categories (CCCs).

## Computable functions and lambda calculus

A function*F*:

**N**â†’

**N**of natural numbers is a computable function if and only if there exists a lambda expression

*f*such that for every pair of

*x*,

*y*in

**N**,

*F*(

*x*)=

*y*if and only if

*f*

*x*=Î²

*y*, where

*x*and

*y*are the Church numerals corresponding to

*x*and

*y*, respectively and =Î² meaning equivalence with beta reduction. This is one of the many ways to define computability; see the Churchâ€“Turing thesis for a discussion of other approaches and their equivalence.

## Undecidability of equivalence

There is no algorithm that takes as input two lambda expressions and outputs TRUE or FALSE depending on whether or not the two expressions are equivalent. This was historically the first problem for which undecidability could be proven. As is common for a proof of undecidability, the proof shows that no computable function can decide the equivalence. Church's thesis is then invoked to show that no algorithm can do so.Church's proof first reduces the problem to determining whether a given lambda expression has a*normal form*. A normal form is an equivalent expression that cannot be reduced any further under the rules imposed by the form. Then he assumes that this predicate is computable, and can hence be expressed in lambda calculus. Building on earlier work by Kleene and constructing a GÃ¶del numbering for lambda expressions, he constructs a lambda expression

*e*that closely follows the proof of GÃ¶del's first incompleteness theorem. If

*e*is applied to its own GÃ¶del number, a contradiction results.

## Lambda calculus and programming languages

As pointed out by Peter Landin's 1965 paper "A Correspondence between ALGOL 60 and Church's Lambda-notation"JOURNAL,weblink A Correspondence between ALGOL 60 and Church's Lambda-notation, P. J., Landin, Peter Landin, Communications of the ACM, 8, 2, 1965, 89â€“101, 10.1145/363744.363749, , sequential procedural programming languages can be understood in terms of the lambda calculus, which provides the basic mechanisms for procedural abstraction and procedure (subprogram) application.### Anonymous functions

For example, in Lisp the "square" function can be expressed as a lambda expression as follows:(lambda (x) (* x x))The above example is an expression that evaluates to a first-class function. The symbol lambda creates an anonymous function, given a list of parameter names, (x) â€“ just a single argument in this case, and an expression that is evaluated as the body of the function, (* x x). Anonymous functions are sometimes called lambda expressions.For example, Pascal and many other imperative languages have long supported passing subprograms as arguments to other subprograms through the mechanism of function pointers. However, function pointers are not a sufficient condition for functions to be first class datatypes, because a function is a first class datatype if and only if new instances of the function can be created at run-time. And this run-time creation of functions is supported in Smalltalk, JavaScript, and more recently in Scala, Eiffel ("agents"), C# ("delegates") and C++11, among others.### Reduction strategies

{{details|Evaluation strategy}}Whether a term is normalising or not, and how much work needs to be done in normalising it if it is, depends to a large extent on the reduction strategy used. The distinction between reduction strategies relates to the distinction in functional programming languages between eager evaluation and lazy evaluation.- Full beta reductions: Any redex can be reduced at any time. This means essentially the lack of any particular reduction strategyâ€”with regard to reducibility, "all bets are off".
- Applicative order: The rightmost, innermost redex is always reduced first. Intuitively this means a function's arguments are always reduced before the function itself. Applicative order always attempts to apply functions to normal forms, even when this is not possible.
- Most programming languages (including Lisp, ML and imperative languages like C and Java) are described as "strict", meaning that functions applied to non-normalising arguments are non-normalising. This is done essentially using applicative order, call by value reduction (see below), but usually called "eager evaluation".
- Normal order: The leftmost, outermost redex is always reduced first. That is, whenever possible the arguments are substituted into the body of an abstraction before the arguments are reduced.
- Call by name: As normal order, but no reductions are performed inside abstractions. For example, Î»
*x*.(Î»*x*.*x*)*x*is in normal form according to this strategy, although it contains the redex (Î»*x*.*x*)*x*. - Call by value: Only the outermost redexes are reduced: a redex is reduced only when its right hand side has reduced to a value (variable or lambda abstraction).
- Call by need: As normal order, but function applications that would duplicate terms instead name the argument, which is then reduced only "when it is needed". Called in practical contexts "lazy evaluation". In implementations this "name" takes the form of a pointer, with the redex represented by a thunk.

**Î©**= Ï‰Ï‰ where

**Ï‰**= Î»

*x*.

*xx*. This entire expression contains only one redex, namely the whole expression; its reduct is again

**Î©**. Since this is the only available reduction,

**Î©**has no normal form (under any evaluation strategy). Using applicative order, the expression

**KIÎ©**= (Î»

*x*.Î»

*y*.

*x*) (Î»

*x*.

*x*)

**Î©**is reduced by first reducing

**Î©**to normal form (since it is the rightmost redex), but since

**Î©**has no normal form, applicative order fails to find a normal form for

**KIÎ©**.In contrast, normal order is so called because it always finds a normalising reduction, if one exists. In the above example,

**KIÎ©**reduces under normal order to

*I*, a normal form. A drawback is that redexes in the arguments may be copied, resulting in duplicated computation (for example, (Î»

*x*.

*xx*) ((Î»

*x*.

*x*)

*y*) reduces to ((Î»

*x*.

*x*)

*y*) ((Î»

*x*.

*x*)

*y*) using this strategy; now there are two redexes, so full evaluation needs two more steps, but if the argument had been reduced first, there would now be none).The positive tradeoff of using applicative order is that it does not cause unnecessary computation, if all arguments are used, because it never substitutes arguments containing redexes and hence never needs to copy them (which would duplicate work). In the above example, in applicative order (Î»

*x*.

*xx*) ((Î»

*x*.

*x*)

*y*) reduces first to (Î»

*x*.

*xx*)

*y*and then to the normal order

*yy*, taking two steps instead of three.Most

*purely*functional programming languages (notably Miranda and its descendents, including Haskell), and the proof languages of theorem provers, use

*lazy evaluation*, which is essentially the same as call by need. This is like normal order reduction, but call by need manages to avoid the duplication of work inherent in normal order reduction using

*sharing*. In the example given above, (Î»

*x*.

*xx*) ((Î»

*x*.

*x*)

*y*) reduces to ((Î»

*x*.

*x*)

*y*) ((Î»

*x*.

*x*)

*y*), which has two redexes, but in call by need they are represented using the same object rather than copied, so when one is reduced the other is too.

### A note about complexity

While the idea of beta reduction seems simple enough, it is not an atomic step, in that it must have a non-trivial cost when estimating computational complexity.JOURNAL, R., Statman, Richard Statman,weblink The typed Î»-calculus is not elementary recursive, Theoretical Computer Science, 1979, 9, 1, 73â€“81, 10.1016/0304-3975(79)90007-0, To be precise, one must somehow find the location of all of the occurrences of the bound variable*V*in the expression

*E*, implying a time cost, or one must keep track of these locations in some way, implying a space cost. A naÃ¯ve search for the locations of

*V*in

*E*is

*O*(

*n*) in the length

*n*of

*E*. This has led to the study of systems that use explicit substitution. Sinot's director stringsJOURNAL, F.-R., Sinot,weblink Director Strings Revisited: A Generic Approach to the Efficient Representation of Free Variables in Higher-order Rewriting, Journal of Logic and Computation, 15, 2, 201â€“218, 2005, 10.1093/logcom/exi010, {{dead link|date=December 2017 |bot=InternetArchiveBot |fix-attempted=yes }} offer a way of tracking the locations of free variables in expressions.

### Parallelism and concurrency

The Churchâ€“Rosser property of the lambda calculus means that evaluation (Î²-reduction) can be carried out in*any order*, even in parallel. This means that various nondeterministic evaluation strategies are relevant. However, the lambda calculus does not offer any explicit constructs for parallelism. One can add constructs such as Futures to the lambda calculus. Other process calculi have been developed for describing communication and concurrency.

### Optimal reduction

In LÃ©vy's 1988 paper "Sharing in the Evaluation of lambda Expressions", he defines a notion of optimal sharing, such that no work is*duplicated*. For example, performing a beta reduction in normal order on (Î»

*x*.

*xx*) (II) reduces it to II (II). The argument II is duplicated by the application to the first lambda term. If the reduction was done in an applicative order first, we save work because work is not duplicated: (Î»

*x*.

*xx*) (II) reduces to (Î»

*x*.

*xx*) I. On the other hand, using applicative order can result in redundant reductions or even possibly never reduce to normal form. For example, performing a beta reduction in normal order on (Î»

*f*.f I) (Î»y.(Î»

*x*.

*xx*) (y I)) yields (Î»y.(Î»

*x*.

*xx*) (y I)) I, (Î»

*x*.

*xx*) (II) which we know we can do without duplicating work. Doing the same but in applicative order yields (Î»

*f*.f I) (Î»y.y I (y I)), (Î»y.y I (y I)) I, I I (I I), and now work is duplicated.LÃ©vy shows the existence of lambda terms where there

*does not exist*a sequence of reductions which reduces them without duplicating work. The below lambda term is such an example.((Î»g.(g(g(Î»x.x))))(Î»h.((Î»f.(f(f(Î»z.z))))(Î»w.(h(w(Î»y.y)))))))It is composed of three similar terms, x=((Î»g. ... ) (Î»h.y)) and y=((Î»f. ...) (Î»w.z) ), and finally z=Î»w.(h(w(Î»y.y))). There are only two possible beta reductions to be done here, on x and on y. Reducing the outer x term first results in the inner y term being duplicated, and each copy will have to be reduced, but reducing the inner y term first will duplicate its argument z, which will cause work to be duplicated when the values of h and w are made known. Incidentally, the above term reduces to the identity function (Î»y.y), and is constructed by making wrappers which make the identity function available to the binders g=Î»h..., f=Î»w..., h=Î»x.x (at first), and w=Î»z.z (at first), all of which are applied to the innermost term Î»y.y.The precise notion of duplicated work relies on noticing that after the first reduction of I I is done, the value of the other I I can be determined, because they have the same structure (and in fact they have exactly the same values), and result from a common ancestor. Such similar structures can each be assigned a label that can be tracked across reductions. If a name is assigned to the redex that produces all the resulting II terms, and then all duplicated occurrences of II can be tracked and reduced in one go. However, it is not obvious that a redex will produce the II term. Identifying the structures that are similar in different parts of a lambda term can involve a complex algorithm and can possibly have a complexity equal to the history of the reduction itself.While LÃ©vy defines the notion of optimal sharing, he does not provide an algorithm to do it. In Vincent van Oostrom, Kees-Jan van de Looij, and Marijn Zwitserlood's paper

*Lambdascope: Another optimal implementation of the lambda-calculus*, they provide such an algorithm by transforming lambda terms into interaction nets, which are then reduced. Roughly speaking, the resulting reduction is optimal because every term that would have the same labels as per LÃ©vy's paper would also be the same graph in the interaction net. In the paper, they mention that their prototype implementation of Lambdascope performs as well as the

*optimised*version of the reference optimal higher order machine BOHM.More details can be found in the short article About the efficient reduction of lambda terms.

## Semantics

The fact that lambda calculus terms act as functions on other lambda calculus terms, and even on themselves, led to questions about the semantics of the lambda calculus. Could a sensible meaning be assigned to lambda calculus terms? The natural semantics was to find a set*D*isomorphic to the function space

*D*â†’

*D*, of functions on itself. However, no nontrivial such

*D*can exist, by cardinality constraints because the set of all functions from

*D*to

*D*has greater cardinality than

*D*, unless

*D*is a singleton set.In the 1970s, Dana Scott showed that, if only continuous functions were considered, a set or domain

*D*with the required property could be found, thus providing a model for the lambda calculus.This work also formed the basis for the denotational semantics of programming languages.

## Variations and extensions

These extensions are in the lambda cube:- Typed lambda calculus â€“ Lambda calculus with typed variables (and functions)
- System F â€“ A typed lambda calculus with type-variables
- Calculus of constructions â€“ A typed lambda calculus with types as first-class values

- Binary lambda calculus â€“ A version of lambda calculus with binary I/O, a binary encoding of terms, and a designated universal machine.
- Lambda-mu calculus â€“ An extension of the lambda calculus for treating classical logic

- Kappa calculus â€“ A first-order analogue of lambda calculus

- Combinatory logic â€“ A notation for mathematical logic without variables
- SKI combinator calculus â€“ A computational system based on the
**S**,**K**and**I**combinators, equivalent to lambda calculus, but reducible without variable substitutions

## See also

{{colbegin|colwidth=30em}}- Applicative computing systems â€“ Treatment of objects in the style of the lambda calculus
- Cartesian closed category â€“ A setting for lambda calculus in category theory
- Categorical abstract machine â€“ A model of computation applicable to lambda calculus
- Curryâ€“Howard isomorphism â€“ The formal correspondence between programs and proofs
- De Bruijn index â€“ notation disambugating alpha conversions
- De Bruijn notation â€“ notation using postfix modification functiond
- Deductive lambda calculus â€“ The consideration of the problems associated with considering lambda calculus as a Deductive system.
- Domain theory â€“ Study of certain posets giving denotational semantics for lambda calculus
- Evaluation strategy â€“ Rules for the evaluation of expressions in programming languages
- Explicit substitution â€“ The theory of substitution, as used in Î²-reduction
- Functional programming
- Harrop formula â€“ A kind of constructive logical formula such that proofs are lambda terms
- Interaction nets
- Kleeneâ€“Rosser paradox â€“ A demonstration that some form of lambda calculus is inconsistent
- Knights of the Lambda Calculus â€“ A semi-fictional organization of LISP and Scheme hackers
- Krivine machine â€“ An abstract machine to interpret call-by-name in lambda-calculus
- Lambda calculus definition â€“ Formal definition of the lambda calculus.
- Let expression â€“ An expression closely related to a lambda abstraction.
- Minimalism (computing)
- Rewriting â€“ Transformation of formulÃ¦ in formal systems
- SECD machine â€“ A virtual machine designed for the lambda calculus
- To Mock a Mockingbird â€“ An introduction to Haskell (programming language) and lambda calculus
- Universal Turing machine â€“ A formal computing machine that is equivalent to lambda calculus
- Unlambda â€“ An esoteric functional programming language based on combinatory logic

## References

{{Reflist|30em}}## Further reading

- Abelson, Harold & Gerald Jay Sussman. Structure and Interpretation of Computer Programs. The MIT Press. {{isbn|0-262-51087-1}}.
- Hendrik Pieter Barendregt
*Introduction to Lambda Calculus*. - Henk Barendregt, The Impact of the Lambda Calculus in Logic and Computer Science. The Bulletin of Symbolic Logic, Volume 3, Number 2, June 1997.
- Barendregt, Hendrik Pieter,
*The Type Free Lambda Calculus*pp1091â€“1132 of*Handbook of Mathematical Logic*, North-Holland (1977) {{isbn|0-7204-2285-X}} - Cardone and Hindley, 2006. History of Lambda-calculus and Combinatory Logic. In Gabbay and Woods (eds.),
*Handbook of the History of Logic*, vol. 5. Elsevier. - Church, Alonzo,
*An unsolvable problem of elementary number theory*, American Journal of Mathematics, 58 (1936), pp. 345â€“363. This paper contains the proof that the equivalence of lambda expressions is in general not decidable. - Alonzo Church,
*The Calculi of Lambda-Conversion*({{isbn|978-0-691-08394-0}})JOURNAL, Orrin Frink, Frink Jr., Orrin, Review:*The Calculi of Lambda-Conversion*by Alonzo Church, Bull. Amer. Math. Soc., 1944, 50, 3, 169â€“172,weblink 10.1090/s0002-9904-1944-08090-7, - Kleene, Stephen,
*A theory of positive integers in formal logic*, American Journal of Mathematics, 57 (1935), pp. 153â€“173 and 219â€“244. Contains the lambda calculus definitions of several familiar functions. - Landin, Peter,
*A Correspondence Between ALGOL 60 and Church's Lambda-Notation*, Communications of the ACM, vol. 8, no. 2 (1965), pages 89â€“101. Available from the ACM site. A classic paper highlighting the importance of lambda calculus as a basis for programming languages. - Larson, Jim, weblink" title="web.archive.org/web/20011206080336weblink">
*An Introduction to Lambda Calculus and Scheme*. A gentle introduction for programmers. - Schalk, A. and Simmons, H. (2005) ''An introduction to Î»-calculi and arithmetic with a decent selection of exercises. Notes for a course in the Mathematical Logic MSc at Manchester University.
- de Queiroz, Ruy J.G.B. (2008) "On Reduction Rules, Meaning-as-Use and Proof-Theoretic Semantics".
*Studia Logica*,**90**(2):211â€“247. {{doi|10.1007/s11225-008-9150-5}}. A paper giving a formal underpinning to the idea of 'meaning-is-use' which, even if based on proofs, it is different from proof-theoretic semantics as in the Dummettâ€“Prawitz tradition since it takes reduction as the rules giving meaning. - Hankin, Chris,
*An Introduction to Lambda Calculi for Computer Scientists,*{{isbn|0954300653}}

- Morten Heine SÃ¸rensen, PaweÅ‚ Urzyczyn,
*Lectures on the Curryâ€“Howard isomorphism*, Elsevier, 2006, {{isbn|0-444-52077-5}} is a recent monograph that covers the main topics of lambda calculus from the type-free variety, to most typed lambda calculi, including more recent developments like pure type systems and the lambda cube. It does not cover subtyping extensions. - {{Citation|last=Pierce|first=Benjamin|title=Types and Programming Languages|publisher=MIT Press|year=2002|isbn=0-262-16209-1}} covers lambda calculi from a practical type system perspective; some topics like dependent types are only mentioned, but subtyping is an important topic.

*Some parts of this article are based on material from FOLDOC, used with permission.*

## External links

- Graham Hutton, Lambda Calculus, a short (12 minutes) Computerphile video on the Lambda Calculus
- Helmut Brandl,
*A Step by Step Introduction into Lambda Calculus* - {{springer|title=Lambda-calculus|id=p/l057000}}
- Achim Jung,
*A Short Introduction to the Lambda Calculus*-(PDF) - Dana Scott,
*A timeline of lambda calculus*-(PDF) - David C. Keenan,
*To Dissect a Mockingbird: A Graphical Notation for the Lambda Calculus with Animated Reduction* - RaÃºl Rojas,
*A Tutorial Introduction to the Lambda Calculus*-(PDF) - Peter Selinger,
*Lecture Notes on the Lambda Calculus*-(PDF) - L. Allison,
*Some executable Î»-calculus examples* - Georg P. Loczewski,
*The Lambda Calculus and A++* - Bret Victor,
*Alligator Eggs: A Puzzle Game Based on Lambda Calculus* *Lambda Calculus*on Safalra's Website*{{planetmath reference|id=2788|title=Lambda Calculus}}*- LCI Lambda Interpreter a simple yet powerful pure calculus interpreter
- Lambda Calculus links on Lambda-the-Ultimate
- Mike Thyer, Lambda Animator, a graphical Java applet demonstrating alternative reduction strategies.
- Implementing the Lambda calculus using C++ Templates
- Marius Buliga,
*Graphic lambda calculus* - weblink" title="web.archive.org/web/20160729210437weblink">
*Lambda Calculus as a Workflow Model*by Peter Kelly, Paul Coddington, and Andrew Wendelborn; mentions graph reduction as a common means of evaluating lambda expressions and discusses the applicability of lambda calculus for distributed computing (due to the Churchâ€“Rosser property, which enables parallel graph reduction for lambda expressions). - Shane Steinert-Threlkeld, "Lambda Calculi",
*Internet Encyclopedia of Philosophy* - Anton Salikhmetov,
*Macro Lambda Calculus*

**- content above as imported from Wikipedia**

- "

- time: 11:19pm EDT - Tue, Jun 18 2019

- "

__lambda calculus__" does not exist on GetWiki (yet)- time: 11:19pm EDT - Tue, Jun 18 2019

[ this remote article is provided by Wikipedia ]

LATEST EDITS [ see all ]

GETWIKI 09 MAY 2016

GETWIKI 18 OCT 2015

GETWIKI 20 AUG 2014

GETWIKI 19 AUG 2014

GETWIKI 18 AUG 2014

© 2019 M.R.M. PARROTT | ALL RIGHTS RESERVED