# Function composition: Difference between revisions

Line 1: | Line 1: | ||

'''Function composition''' refers to the "gluing" together of two or more [[function]]s using a [[dyadic operator]] or a [[train]] such that the functions are applied to the [[argument]](s) as normal, but in a particular pattern. The term [[wikipedia:function composition|function composition]] comes from [[traditional mathematics]] where it is used for a function <math>h(x)=f(g(x))</math> when written as <math> h(x) = (f \circ g)(x)</math>. APL generalises this idea to [[dyadic function]]s, allowing various patterns of application in addition to the simple application of one [[monadic function]] to the result of another monadic function. | '''Function composition''' refers to the "gluing" together of two or more [[function]]s using a [[dyadic operator]] or a [[train]] such that the functions are applied to the [[argument]](s) as normal, but in a particular pattern. The term [[wikipedia:function composition|function composition]] comes from [[traditional mathematics]] where it is used for a function <math>h(x)=f(g(x))</math> when written as <math> h(x) = (f \circ g)(x)</math>. APL generalises this idea to [[dyadic function]]s, allowing various patterns of application in addition to the simple application of one [[monadic function]] to the result of another monadic function. | ||

== Common compositions == | == Common compositions == | ||

[[Reverse Compose]] and [[Beside]] treat their arguments in an asymmetric way. Their patterns can be visualised as follows: | [[Reverse Compose]] and [[Beside]] treat their arguments in an asymmetric way. They can be seen as using a [[monadic function]] to pre-process the left or right argument, respectively, before proceeding to apply a main function. Their patterns can be visualised as follows: | ||

{| class=wikitable | {| class=wikitable | ||

Line 9: | Line 9: | ||

|} | |} | ||

[[Atop (operator)|Atop]] and [[Over]] treat their arguments in a symmetric way. Their patterns can be visualised as follows: | [[Atop (operator)|Atop]] and [[Over]] treat their arguments in a symmetric way. They can be seen as using a monadic function to post-process the result or pre-process the argument(s) of a main function. Their patterns can be visualised as follows: | ||

{| class=wikitable | {| class=wikitable | ||

! Atop !! Over | ! Atop !! Over | ||

Line 16: | Line 16: | ||

|} | |} | ||

[[Tacit_programming#trains|Trains]] provide a way to apply a function to the result(s) of one (for 2-trains) or two (for 3-trains) other functions. These patterns are also called Atop and Fork, and can be visualised as follows: | |||

{| class=wikitable | {| class=wikitable | ||

! 2-train !! 3-train | ! 2-train !! 3-train | ||

Line 23: | Line 23: | ||

|} | |} | ||

The <source lang=apl inline>∘</source> | The operator represented by [[Jot]] (<source lang=apl inline>∘</source>, in this context called [[Bind]]) and the 3-train can also be used with constant arrays, then treating the arrays (<source lang=apl inline>A</source>) as constant functions, much as if they were used as operands to the [[Constant]] operator (<source lang=apl inline>A⍨</source>): | ||

{| class=wikitable | {| class=wikitable | ||

! Bind !! 3-train | ! Bind !! 3-train |

## Revision as of 07:05, 1 July 2022

**Function composition** refers to the "gluing" together of two or more functions using a dyadic operator or a train such that the functions are applied to the argument(s) as normal, but in a particular pattern. The term function composition comes from traditional mathematics where it is used for a function when written as . APL generalises this idea to dyadic functions, allowing various patterns of application in addition to the simple application of one monadic function to the result of another monadic function.

## Common compositions

Reverse Compose and Beside treat their arguments in an asymmetric way. They can be seen as using a monadic function to pre-process the left or right argument, respectively, before proceeding to apply a main function. Their patterns can be visualised as follows:

Reverse Compose | Beside |
---|---|

Atop and Over treat their arguments in a symmetric way. They can be seen as using a monadic function to post-process the result or pre-process the argument(s) of a main function. Their patterns can be visualised as follows:

Atop | Over |
---|---|

Trains provide a way to apply a function to the result(s) of one (for 2-trains) or two (for 3-trains) other functions. These patterns are also called Atop and Fork, and can be visualised as follows:

2-train | 3-train |
---|---|

The operator represented by Jot (`∘`

, in this context called Bind) and the 3-train can also be used with constant arrays, then treating the arrays (`A`

) as constant functions, much as if they were used as operands to the Constant operator (`A⍨`

):

Bind | 3-train |
---|---|

### Summary of rules

The above compositions can be summarised as follows:

` (f⍛g ) ⍵`

`( f ⍵) g ⍵ `

`⍺ (f⍛g ) ⍵`

`( f ⍺) g ⍵ `

` ( g∘h) ⍵`

` g ( h ⍵)`

`⍺ ( g∘h) ⍵`

` ⍺ g ( h ⍵)`

` ( g⍤h) ⍵`

` g ( h ⍵)`

`⍺ ( g⍤h) ⍵`

` g (⍺ h ⍵)`

` ( g⍥h) ⍵`

` g ( h ⍵)`

`⍺ ( g⍥h) ⍵`

`( h ⍺) g ( h ⍵)`

` ( g h) ⍵`

` g ( h ⍵)`

`⍺ ( g h) ⍵`

` g (⍺ h ⍵)`

` (f g h) ⍵`

`( f ⍵) g ( h ⍵)`

`⍺ (f g h) ⍵`

`(⍺ f ⍵) g (⍺ h ⍵)`

` (A∘g ) ⍵`

` A g ⍵ `

` ( g∘A) ⍵`

` ⍵ g A `

` (A g h) ⍵`

` A g ( h ⍵)`

`⍺ (A g h) ⍵`

` A g (⍺ h ⍵)`

## Additional compositions

Additional compositions are possible, even without using an argument more than once or applying a function to its own result. However, most of these are rather trivial shuffled-around versions of the above three. For example, one could define an operator identical to Atop, only that it applies the right operand to the result of the left operand, that is `{⍵⍵ ⍺ ⍺⍺ ⍵}`

.

When Dyalog added Atop and Over, it was with the reasoning that these were the only compositions where the leftmost function acted as the "root" function in the evaluation tree, while the arguments were used each on their respective sides of the constituent functions:

Of note here is `f⍨∘g⍨`

which is equivalent to — although with swapped operands — Reverse-compose `⍛`

(also called *Before*), and the mirrored version of Beside `∘`

(also known as *Compose* and *After*), because it is the only such variation that has been implemented, namely in dzaima/APL and Extended Dyalog APL.

A compositional operator that isn't just a shuffled around version of the basic three, is one that applies one operand between the other operand's dyadic result and the result of that other operand's result when swapped: `{(⍵ ⍵⍵ ⍺) ⍺⍺ (⍺ ⍵⍵ ⍵)}`

. This operator can for example be used to implement three-way comparison:

```
S ← {(⍵ ⍵⍵ ⍺) ⍺⍺ (⍺ ⍵⍵ ⍵)}
cmp ← -S≤
2 cmp 3
¯1
3 cmp 3
0
4 cmp 3
1
```

## External links

- Dyalog '19: Tacit Techniques with Dyalog version 18.0 Operators
- Dyalog webinar: Language Features of Dyalog version 18.0 in Depth

APL features [edit]
| |
---|---|

Built-ins | Primitives (functions, operators) ∙ Quad name |

Array model | Shape ∙ Rank ∙ Depth ∙ Bound ∙ Index (Indexing) ∙ Axis ∙ Ravel ∙ Ravel order ∙ Element ∙ Scalar ∙ Vector ∙ Matrix ∙ Simple scalar ∙ Simple array ∙ Nested array ∙ Cell ∙ Major cell ∙ Subarray ∙ Empty array ∙ Prototype |

Data types | Number (Boolean, Complex number) ∙ Character (String) ∙ Box ∙ Namespace ∙ Function array |

Concepts and paradigms | Conformability (Scalar extension, Leading axis agreement) ∙ Scalar function (Pervasion) ∙ Identity element ∙ Complex floor ∙ Total array ordering ∙ Tacit programming (Function composition, Close composition) ∙ Glyph |

Errors | LIMIT ERROR ∙ RANK ERROR ∙ SYNTAX ERROR ∙ DOMAIN ERROR ∙ LENGTH ERROR ∙ INDEX ERROR ∙ VALUE ERROR |