7Core twigs are flow twigs. The compiler essentially pins a Nock
8formula, or battery of formulas, to the subject.
10All `|` twigs are macros around `$core`. (See the `$core`
11section in [`span`](../span) above.) `$core` uses the subject as
12the payload of a battery, whose arms are compiled with the core
17The rune prefix is `|`. Suffixes: `%` for `:core`, `=` for
18`:gate`, `-` for `:loop`, `.` for `:trap`, `_` for `:door`.
20### `:core`, `|%`, "barcen", `{$core p/(map term twig)}`
24The product: a core with battery `p`. Payload is the subject.
26### `:gate`, `|=`, "bartis", `{$gate p/moss q/twig}
40A `$gate` produces a function from `p` to `q`. `p` is the
41*sample*, or argument. The core has one formula, named `$` (the
42empty name). The payload is of the form `{sample context}`,
43where `context` is the subject of the gate.
45### `:loop`, `|-`, "barhep", `{$loop p/twig}`
59A `$loop` makes a core with one anonymous arm `p`, then takes
62### `:trap`, `|.`, "bardot", `{$trap p/twig}`
74A `$trap` is a deferred value.
76### `:door`, `|_`, "barcab", `{$door p/moss q/(map term twig)}`
78Syntax: *1-fixed*, then *battery*.
89A `gate` is a function; a `door` is the general case of a
90function. Wut? We'll look at this again from the caller's side.
keysesc to close
- j k
- move down, up
- enter
- open
- esc
- back, or up a level
- 1 2 3 4
- readme, files, commits, refs
- /
- filter
- y
- copy the clone command
- c
- compare the chosen commit with another (or shift-click both)
- ?
- show or hide this list