git.iko.soy/urbit.org
on 04b10be help sign in
urbit.org/reference/hoon-errors.md
182 lines 5.6 kB history raw
1+++
2title = "Hoon Errors"
3weight = 6
4template = "doc.html"
5+++
6Ideally your Hoon works perfectly the first time. But...
8## Syntax errors
10When you get a syntax error, you'll see a message like
12```
13syntax error: 10 12
14```
16This is a line and column number; more exactly, the line and
17column of the first byte the parser couldn't interpret as part of
18a correct Hoon file. These values are always correct.
20Usually, the line and column tell you everything you need to
21know. But the worst-case scenario for a syntax error is that,
22somewhere above, you've confused Hoon's tall form by using the
23wrong fanout for a rune. For example, `%+` ([**cenlus**](@/docs/reference/hoon-expressions/rune/cen.md#cenlus),
24a function call whose sample is a cell) has three subhoons:
26```
27%+ foo
28 bar
29baz
30```
32But if you make a mistake and write
34```
35%+ foo
36bar
37```
39the parser will eat the next hoon below and try to treat it as a
40part of the `%+`. This can cause a cascading error somewhere
41below, usually stopped by a `==` or `--`.
43When this happens, don't panic! Binary search actually works
44quite well. Any hoon can be stubbed out as `!!`. Find the
45prefix of your file that compiles, then work forward until
46the actual error appears.
48## Semantic errors
50Now your code parses but doesn't compile.
52### Turn on debugging
54Your first step should be to put a `!:` ("zapcol") rune at the
55top of the file. This is like calling the C compiler with `-g`;
56it tells the Hoon compiler to generate tracing hoons.
58Bear in mind that `!:` breaks tail-call optimization. This is a
59bug, but a relatively low-priority bug. `!.` turns off `!:`.
60Note that `!:` and `!.` are hoon-level, not file-level; you can
61wrap any hoon in either.
63### Error trace
65If you have `!:` on, you'll see an error trace, like
67```
68/~zod/home/0/gen/hello:<[7 3].[11 21]>
69/~zod/home/0/gen/hello:<[8 1].[11 21]>
70/~zod/home/0/gen/hello:<[9 1].[11 21]>
71/~zod/home/0/gen/hello:<[10 1].[11 21]>
72/~zod/home/0/gen/hello:<[11 1].[11 21]>
73/~zod/home/0/gen/hello:<[11 7].[11 21]>
74nest-fail
75```
77The bottom of this trace is the line and column of the hoon which
78failed to compile, then the cause of the error (`nest-fail`).
80Hoon does not believe in inundating you with possibly irrelevant
81debugging information. Your first resort is always to just look
82at the code and try to figure out what's wrong. This practice
83strengthens your Hoon muscles.
85(Consider the opposite extreme; imagine if you had a magic bot
86that always fixed your compiler errors for you. Pro: no time
87wasted on compiler errors. Con: you never learn Hoon.)
89## Common errors
91Moral fiber is all very well and good, but sometimes you're
92stumped. Couldn't the compiler help a little? These messages do
93mean something. Here are the three most common:
95### `nest-fail`
97This is a type mismatch (`nest` is the Hoon typechecker). It
98means you tried to pound a square peg into a round hole.
100What was the peg and what was the hole? Hoon doesn't tell you by
101default, because moral fiber, and also because in too many cases
102trivial errors lead to large intimidating dumps. However, you
103can use the `~!` rune ([**sigzap**](@/docs/reference/hoon-expressions/rune/sig.md#sigzap)) to print the type of
104any hoon in your stack trace.
106For instance, you wrote `(foo bar)` and got a `nest-fail`. Change
107your code to be:
109```
110~! bar
111~! +6.foo
112(foo bar)
113```
115You'll get the same `nest-fail`, but this will show the type of
116`bar`, then the type of the sample of the `foo` gate.
118### `find.foo`
120A `find.foo` error means limb `foo` wasn't found in the subject.
121In other words, "undeclared variable."
123The most common subspecies of `find` error is `find.$`, meaning
124the empty name `$` was not found. This often happens when you
125use a hoon that does not produce a gate/mold, as a gate/mold. For
126instance, `(foo bar)` will give `find.$` if `foo` is not actually a
127function.
129### `mint-vain` and `mint-lost`
131These are errors caused by type inference in pattern matching.
132`mint-vain` means this hoon is never executed. `mint-lost` means
133there's a case in a `?-` ([**wuthep**](@/docs/reference/hoon-expressions/rune/wut.md#wuthep)) that isn't handled.
135## Runtime crashes
137If your code crashes at runtime or overflows the stack, you'll
138see a stack trace that looks just like the trace above. Don't
139confuse runtime crashes with compilation errors, though.
141If your code goes into an infinite loop, kill it with `ctrl-c` (you'll
142need to be developing on the local console; otherwise, the
143infinite loop will time out either too slowly or too fast). The
144stack trace will show what your code was doing when interrupted.
146The counterpart of `~!` for runtime crashes is `~|`
147([**sigbar**](@/docs/reference/hoon-expressions/rune/sig.md#sigbar)):
149```
150~| foo
151(foo bar)
152```
154If `(foo bar)` crashes, the value of `foo` is printed in the
155stack trace. Otherwise, the `~|` has no effect.
157## Debugging printfs
159The worst possibility, of course, is that your code runs but does
160the wrong thing. This is relatively unusual in a typed
161functional language, but it still happens.
163`~&` ([**sigpam**](@/docs/reference/hoon-expressions/rune/sig.md#sigpam)) is Hoon's debugging printf.
164This pretty-prints its argument:
166```
167~& foo
168(foo bar)
169```
171will always print `foo` every time it executes. A variant is
172`~?` ([**sigwut**](@/docs/reference/hoon-expressions/rune/sig.md#sigwut)), which prints only if a condition is
173true:
175```
176~? =(37 (lent foo)) foo
177(foo bar)
178```
180For now, you need to be on the local console to see these debug
181printfs (which are implemented by interpreter hints). This is a
182bug and, like all bugs, will be fixed at some point.