a3d42b7 · urbit.org · git.iko.soy

git.iko.soy/urbit.org

Merge branch 'is-this-right'

commita3d42b72706c45798a241a269635d894700649b2 authorDavid Kerschner <dkerschner@hcoop.net> dateFri 11 Oct 2019, 11:24 (7 years ago) parenteab26ff b8b8932

8 files changed+18−20

compare with master

unifiedsplit

reference/arvo-glossary.md+2−2 reference/hoon-errors.md+9−11 reference/hoon-expressions/irregular.md+1−1 tutorials/arvo/gall.md+1−1 tutorials/hoon/bank-account.md+1−1 tutorials/hoon/conditionals.md+1−1 tutorials/hoon/hoon-syntax.md+2−2 tutorials/nock/_index.md+1−1

reference/arvo-glossary.md+2−2

@@ -43,7 +43,7 @@ dry.

4343 path, which works as if we expanded the callee with the caller's

4444 context.

4545

46−_See [advanced types](/docs/hoon/hoon-expressions/advanced/)_.

46+_See [advanced types](/docs/reference/hoon-expressions/advanced/)_.

4747

4848

4949

@@ -718,7 +718,7 @@ Here's some common structure terminology:

718718

719719#### icon: The type of the mold's range

720720

721−_See [mold hoons](/docs/hoon/hoon-expressions/rune/buc/)._

721+_See [mold hoons](/docs/reference/hoon-expressions/rune/buc/)._

722722

723723### rune

724724

reference/hoon-errors.md+9−11

@@ -21,9 +21,9 @@ Usually, the line and column tell you everything you need to

2121know. But the worst-case scenario for a syntax error is that,

2222somewhere above, you've confused Hoon's tall form by using the

2323wrong fanout for a rune. For example, `%+` ([**cenlus**](@/docs/reference/hoon-expressions/rune/cen.md#cenlus),

24−a function call whose sample is a cell) has three subreferences:

24+a function call whose sample is a cell) has three subhoons:

2525

26−```reference

26+```hoon

2727%+ foo

2828 bar

2929baz

@@ -31,7 +31,7 @@ baz

3131

3232But if you make a mistake and write

3333

34−```reference

34+```hoon

3535%+ foo

3636bar

3737```

@@ -100,13 +100,12 @@ means you tried to pound a square peg into a round hole.

100100What was the peg and what was the hole? Hoon doesn't tell you by

101101default, because moral fiber, and also because in too many cases

102102trivial errors lead to large intimidating dumps. However, you

103−can use the `~!` rune ([**sigzap**](@/docs/reference/hoon-expressions/rune/sig.md#sigzap)) to print the type of

104−any reference in your stack trace.

103+can use the `~!` rune ([**sigzap**](@/docs/reference/hoon-expressions/rune/sig.md#sigzap)) to print the type of any hoon in your stack trace.

105104

106105For instance, you wrote `(foo bar)` and got a `nest-fail`. Change

107106your code to be:

108107

109−```reference

108+```hoon

110109~! bar

111110~! +6.foo

112111(foo bar)

@@ -129,8 +128,7 @@ function.

129128### `mint-vain` and `mint-lost`

130129

131130These are errors caused by type inference in pattern matching.

132−`mint-vain` means this reference is never executed. `mint-lost` means

133−there's a case in a `?-` ([**wuthep**](@/docs/reference/hoon-expressions/rune/wut.md#wuthep)) that isn't handled.

131+`mint-vain` means this hoon is never executed. `mint-lost` means there's a case in a `?-` ([**wuthep**](@/docs/reference/hoon-expressions/rune/wut.md#wuthep)) that isn't handled.

134132

135133## Runtime crashes

136134

@@ -146,7 +144,7 @@ stack trace will show what your code was doing when interrupted.

146144The counterpart of `~!` for runtime crashes is `~|`

147145([**sigbar**](@/docs/reference/hoon-expressions/rune/sig.md#sigbar)):

148146

149−```reference

147+```hoon

150148~| foo

151149(foo bar)

152150```

@@ -163,7 +161,7 @@ functional language, but it still happens.

163161`~&` ([**sigpam**](@/docs/reference/hoon-expressions/rune/sig.md#sigpam)) is Hoon's debugging printf.

164162This pretty-prints its argument:

165163

166−```reference

164+```hoon

167165~& foo

168166(foo bar)

169167```

@@ -172,7 +170,7 @@ will always print `foo` every time it executes. A variant is

172170`~?` ([**sigwut**](@/docs/reference/hoon-expressions/rune/sig.md#sigwut)), which prints only if a condition is

173171true:

174172

175−```reference

173+```hoon

176174~? =(37 (lent foo)) foo

177175(foo bar)

178176```

reference/hoon-expressions/irregular.md+1−1

@@ -241,7 +241,7 @@ See [%sand](@/docs/reference/hoon-expressions/rune/constants.md#warm) for other

241241

242242### Wings

243243

244−[docs](content/docs/hoon/hoon-expressions/limb/wing.md)

244+[docs](content/docs/reference/hoon-expressions/limb/wing.md)

245245`[%wing p=(list limb)]`; a limb search path.

246246`a.b` finds limb `a` within limb `b` ("var" `a` within "var" `b`).

247247

tutorials/arvo/gall.md+1−1

@@ -1064,7 +1064,7 @@ from the command line, which we we did with `:echo 5`

10641064(`:[app-name] [argument(s)]`).

10651065

10661066In this case, `++poke-noun` takes an argument (**sample**) `arg` and

1067−prints it to dojo with `~&` ([sigpam](/docs/hoon/hoon-expressions/rune/sig#sigpam/)).

1067+prints it to dojo with `~&` ([sigpam](/docs/reference/hoon-expressions/rune/sig#sigpam/)).

10681068This is an unusual rune that formally "does nothing", but the interpreter

10691069detects it and printfs the first child, before executing the second as if the

10701070first didn't exist. This is a slightly hacky way of printing to the console,

tutorials/hoon/bank-account.md+1−1

@@ -75,7 +75,7 @@ Each of these arms produces a gate which takes an `@ud` argument. Each of these

7575+>.$(balance (add balance amount))

7676```

7777

78−`+>` is [wing syntax](/docs/hoon/hoon-expressions/limb/limb/). This particularly wing construction looks for the the tail of the tail (the third element) in `$`, the subject of the gate we are in, which is the entire `new-account` door. We change `balance` to be the result of adding `balance` and `amount` and produce the door as the result. `withdraw` functions the same way only doing subtraction instead of addition.

78+`+>` is [wing syntax](/docs/reference/hoon-expressions/limb/limb/). This particularly wing construction looks for the the tail of the tail (the third element) in `$`, the subject of the gate we are in, which is the entire `new-account` door. We change `balance` to be the result of adding `balance` and `amount` and produce the door as the result. `withdraw` functions the same way only doing subtraction instead of addition.

7979

8080It's important to notice that the sample, `balance`, is stored as part of the door rather than existing outside of it.

8181

tutorials/hoon/conditionals.md+1−1

@@ -70,6 +70,6 @@ We only went into three "wut" runes in our walkthrough, but there are many other

7070

7171- `?|` takes an indefinite number of children. It's the logical "or" operator. It checks if at least one of its children is true.

7272

73−To see an exhaustive list of "wut" runes, check out the [reference documentation on conditionals](/docs/hoon/hoon-expressions/rune/wut/).

73+To see an exhaustive list of "wut" runes, check out the [reference documentation on conditionals](/docs/reference/hoon-expressions/rune/wut/).

7474

7575### [Next Up: Reading -- Lists](../lists)

tutorials/hoon/hoon-syntax.md+2−2

@@ -309,10 +309,10 @@ Standard library functions are often built with other standard library functions

309309

310310The Hoon syntax can be intimidating for the uninitiated, so it's good to remember where you can look up expressions can be found. The [reference section](/docs/reference/) itself is a good place to find the reference materials that you need. These children sections are likely to be useful:

311311

312−- The [Runes](/docs/hoon/hoon-expressions/) page will show you how to use any Hoon rune.

312+- The [Runes](/docs/reference/hoon-expressions/) page will show you how to use any Hoon rune.

313313- The [Cheat sheet](/docs/reference/cheat-sheet/) is a more compact place to look up rune expressions.

314314- The [Standard library](/docs/reference/library/) section has its sub-pages arranged by category. So arithmetic functions, for example, are all found on the same page.

315−- The [Hoon Style Guide](/docs/hoon/style/) will show you how to write your Hoon code so that it's idiomatic and easily understood by others.

315+- The [Hoon Style Guide](/docs/reference/style/) will show you how to write your Hoon code so that it's idiomatic and easily understood by others.

316316

317317### Debugging

318318

tutorials/nock/_index.md+1−1

@@ -9,7 +9,7 @@ aliases = ["docs/learn/nock/"]

1010Nock is the low-level functional programming language that is interpreted by Vere. You don't need to know Nock to write Hoon, or even to work on most parts of Vere. But if you want to understand the foundations of Urbit and are mathematically-inclined, dive right in.

1111

12−## [Nock Definition](@/docs/tutorials//nock/definition.md)

12+## [Nock Definition](@/docs/tutorials/nock/definition.md)

1313

1414The Nock specification.

1515