Reduction strategy

In rewriting, a reduction strategy or rewriting strategy is a relation specifying a rewrite for each object or term, compatible with a given reduction relation.^[1] Some authors use the term to refer to an evaluation strategy.^[2][3]

Definitions[]

Formally, for an abstract rewriting system ${\displaystyle (A,\to )}$, a reduction strategy ${\displaystyle \to _{S}}$ is a binary relation on ${\displaystyle A}$ with ${\displaystyle \to _{S}\subseteq {\overset {+}{\to }}}$ , where ${\displaystyle {\overset {+}{\to }}}$ is the transitive closure of ${\displaystyle \to }$ (but not the reflexive closure).^[1]

A one step reduction strategy is one where ${\displaystyle \to _{S}\subseteq \to }$. Otherwise it is a many step strategy.^[4]

A deterministic strategy is one where ${\displaystyle \to _{S}}$ is a partial function, i.e. for each ${\displaystyle a\in A}$ there is at most one ${\displaystyle b}$ such that ${\displaystyle a\to _{S}b}$. Otherwise it is a nondeterministic strategy.^[4]

Term rewriting[]

In a term rewriting system a rewriting strategy specifies, out of all the reducible subterms (redexes), which one should be reduced (contracted) within a term.

One-step strategies for term rewriting include:^[4]

• leftmost-innermost: in each step the leftmost of the innermost redexes is contracted, where an innermost redex is a redex not containing any redexes^[5]
• leftmost-outermost: in each step the leftmost of the outermost redexes is contracted, where an outermost redex is a redex not contained in any redexes^[5]
• rightmost-innermost, rightmost-outermost: similarly

Many-step strategies include:^[4]

• parallel-innermost: reduces all innermost redexes simultaneously. This is well-defined because the redexes are pairwise disjoint.
• parallel-outermost: similarly
• Gross-Knuth reduction,^[6] also called full substitution or Kleene reduction:^[4] all redexes in the term are simultaneously reduced

Parallel outermost and Gross-Knuth reduction are hypernormalizing for all almost-orthogonal term rewriting systems, meaning that these strategies will eventually reach a normal form if it exists, even when performing (finitely many) arbitrary reductions between successive applications of the strategy.^[7]

Stratego is a domain-specific language designed specifically for programming term rewriting strategies.^[8]

Lambda calculus[]

In the context of the lambda calculus, normal-order reduction refers to leftmost-outermost reduction in the sense given above.^[9] Sometimes normal order reduction is simply called leftmost reduction, as the leftmost-outermost redex appears leftmost when the term is written out as a string of characters.^[10] Normal-order reduction is normalizing, in the sense that if a term has a normal form, then normal‐order reduction will eventually reach it, hence the name normal. This is known as the standardization theorem.^[11][12]

Applicative order reduction refers to leftmost-innermost reduction.^[9] In contrast to normal order, applicative order reduction may not terminate, even when the term has a normal form.^[9] For example, using applicative order reduction, the following sequence of reductions is possible:

But using normal-order reduction, the same starting point reduces quickly to normal form:

Full β-reduction refers to the nondeterministic one-step strategy that allows reducing any redex at each step.^[3] Takahashi's parallel β-reduction is the strategy that reduces all redexes in the term simultaneously.^[13]

Weak reduction[]

Normal and applicative order reduction are strong in that they allow reduction under lambda abstractions. In contrast, weak reduction does not reduce under a lambda abstraction.^[14] Call-by-name reduction is the weak reduction strategy that reduces the leftmost outermost redex not inside a lambda abstraction, while call-by-value reduction is the weak reduction strategy that reduces the leftmost innermost redex not inside a lambda abstraction. These strategies were devised to reflect the call-by-name and call-by-value evaluation strategies.^[15] In fact, applicative order reduction was also originally introduced to model the call-by-value parameter passing technique found in Algol 60 and modern programming languages. When combined with the idea of weak reduction, the resulting call-by-value reduction is indeed a faithful approximation.^[16]

Unfortunately, weak reduction is not confluent,^[14] and the traditional reduction equations of the lambda calculus are useless, because they suggest relationships that violate the weak evaluation regime.^[16] However, it is possible to extend the system to be confluent by allowing a restricted form of reduction under an abstraction, in particular when the redex does not involve the variable bound by the abstraction.^[14] For example, λx.(λy.x)z is in normal form for a weak reduction strategy because the redex (λy.x)z is contained in a lambda abstraction. But the term λx.(λy.y)z can still be reduced under the extended weak reduction strategy, because the redex (λy.y)z does not refer to x.^[17]

Optimal reduction[]

Optimal reduction is motivated by the existence of lambda terms where there does not exist a sequence of reductions which reduces them without duplicating work. For example, consider

((λ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 β-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.^[a]

Optimal reduction is not a reduction strategy for the lambda calculus in a strict sense because performing β-reduction loses the information about the substituted redexes being shared. Instead it is defined for the labelled lambda calculus, an annotated lambda calculus which captures a precise notion of the work that should be shared.^{[18]: 113–114}

Labels consist of a countably infinite set of atomic labels, and concatenations ${\displaystyle ab}$, overlinings ${\displaystyle {\overline {a}}}$ and underlinings ${\displaystyle {\underline {a}}}$ of labels. A labelled term is a lambda calculus term where each subterm has a label. The standard initial labeling of a lambda term gives each subterm a unique atomic label.^[18]: 132 Labelled β-reduction is given by:^[19]

where ${\displaystyle \cdot }$ concatenates labels, ${\displaystyle \beta \cdot T^{\alpha }=T^{\beta \alpha }}$, and substitution ${\displaystyle M[x\mapsto N]}$ is defined as follows (using the Barendregt convention):^[19]

The system can be proven to be confluent. Optimal reduction is then defined to be normal order or leftmost-outermost reduction using reduction by families, i.e. the parallel reduction of all redexes with the same function part label.^[20]

A practical algorithm for optimal reduction was first described in 1989,^[21] more than a decade after optimal reduction was first defined in 1974.^[22] The Bologna Optimal Higher-order Machine (BOHM) is a prototype implementation of an extension of the technique to interaction nets.^{[18]: 362 [23]} Lambdascope is a more recent implementation of optimal reduction, also using interaction nets.^[24][b]

Call by need reduction[]

Call by need reduction can be defined similarly to optimal reduction as weak leftmost-outermost reduction using parallel reduction of redexes with the same label, for a slightly different labelled lambda calculus.^[14] An alternate definition changes the beta rule to find the "demanded" computation. This requires extending the beta rule to allow reducing terms that are not syntactically adjacent, so this definition is similar to the labelled definition in that they are both reduction strategies for variations of the lambda calculus.^[25] As with call-by-name and call-by-value, call-by-need reduction was devised to mimic the behavior of the evaluation strategy known as "call-by-need" or lazy evaluation.

See also[]

• Reduction system
• Reduction semantics
• Thunk

Notes[]

References[]

External links[]

• Lambda calculus reduction workbench