git.iko.soy/urbit.org
on 8564483 help sign in
urbit.org/docs/arvo/basic.md
322 lines 10 kB history raw
1---
2navhome: /docs
3sort: 1
4next: true
5title: Hoon refresher / crash course
6---
8# Basic Hoon
10This recapitulates material you've already learned in Core Hoon.
11It will be a very abrupt tutorial if you don't know Hoon already,
12but it may be enough in and of itself. If you don't find it obvious at first
13glance, read it over again.
15Our goal is to get you programming interesting and useful things
16as soon as possible. To get there, we have to quickly cover some
17of the fundamentals of hoon. To do this, we'll walk through two
18simple programs: the first [Project
19Euler](https://projecteuler.net/) problem and
20[fizzbuzz](https://en.wikipedia.org/wiki/Fizz_buzz).
22To run this code, you'll need an urbit, and will have to copy the [examples repo](https://github.com/urbit/examples) into it.
24If you haven't installed
25urbit yet, check out the [installation
26instructions](/docs/user/install). Once urbit is
27installed, take a look at the [basic
28operation](/docs/user/basic) of your urbit.
30If you haven't copied in the examples repo, running the following commands from your urbit directory should do the trick:
32`cp -r {wherever-you've-pulled-to}/examples/gall/*/ arvo/`
33`cp -r {wherever-you've-pulled-to}/examples/dojo/*/ arvo/`
35Run an example to ensure it worked:
37 ~fintud-macrep:dojo> +examples-euler1
38 233.168
40## Euler 1
42Let's check out the code for Euler 1. First, the problem:
44```
45If we list all the natural numbers below 10 that are multiples of
463 or 5, we get 3, 5, 6 and 9. The sum of these multiples is 23.
48Find the sum of all the multiples of 3 or 5 below 1000.
49```
51Here is the hoon solution (which should be in your pier directory
52under `/gen/examples/euler1`):
54```
55:: project euler 1
56:: https://projecteuler.net/problem=1
57:: run in dojo with +examples-euler1
58::
59:::: /hoon/euler1/examples/gen
60 ::
61:- %say |= *
62:- %noun
63=< (sum 1.000)
64::
65:::: ~sivtyv-barnel
66 ::
67|%
68++ three
69 |= a/@
70 =| b/@
71 |- ^- @u
72 ?: (lth a b)
73 0
74 (add b $(b (add 3 b)))
76++ five
77 |= a/@
78 =| b/@
79 |- ^- @
80 ?: (lte a b)
81 0
82 ?: =((mod b 3) 0)
83 $(b (add b 5))
84 (add b $(b (add b 5)))
86++ sum
87 |= a/@u
88 (add (five a) (three a))
89--
90```
93<blockquote class="blockquote">
94Hoon is not generally whitespace sensitive, but we do have two
95different kinds of whitespace: a single space and a gap, which
96is two or more spaces or a linebreak. Tabs are taboo. Do not
97use them. Really. For a more detailed explanation of when to
98use spaces vs. gaps, see the syntax section before the first
99excercises.
100</blockquote>
103### Lines 1-11:
105Any line that begins with `::` is a comment.
107 :- %say |= *
108 :- %noun
109 =< (sum 1.000)
111All you need to know about the lines above is that they call the
112`++sum` function with an argument of `1.000`. We'll cover them in
113more detail later.
115### How to form expressions
117Hoon does not typically use reserved words to form expressions. Instead,
118expressions are formed with runes--diagraphs of two
119ascii symbols. Each rune takes a specific number of
120children--either expressions formed by other runes or literals
121that produce their own value (some runes take n children, and are usually closed with `==`).
123For example, the rune `?:` from line 17 is the classic
124'if-then-else' statement, and thus takes three children:
126 ?: (lth a b) :: if first child evals to true
127 0 :: then produce result of second
128 (add b $(b (add 3 b))) :: else, produce result of third
130Since runes are such a fundamental structure in Hoon, we found
131ourselves speaking them out loud frequently. It quickly grew
132cumbersome to have to say "question mark, colon" to describe
133`?:`. To alleviate this problem, we came up with our own naming
134scheme: each ascii glyph has a single syllable pronunciation
135phonetically designed to be both easily remembered and easily
136pronounced in conjunction with the other glyphs (when forming a
137rune).
139See the entire naming schema below/or link to it:
141```
142 ace [1 space] gal < pel (
143 bar | gap [>1 space, nl] per )
144 bas \ gar > sel [
145 buc $ hax # sem ;
146 cab _ hep - ser ]
147 cen % kel { soq '
148 col : ker } tar *
149 com , ket ^ tec `
150 doq " lus + tis =
151 dot . pam & wut ?
152 fas / pat @ zap !
153```
155Using our naming scheme `?:` is said 'wut col'.
157For those that would prefer to use reserved words to form expressions, you can substitute a rune's keyword--which you can find in `++twig` in `/arvo/hoon.hoon`--for the rune. For example, here's the code for `?:` in `++twig`:
159`{$if p/twig q/twig r/twig} :: ?: if/then/else`
161Instead of:
163```
164?:(=(1 2) 'this is true' 'this is false')
165'this is false'`
166```
167You can write:
169```
170if(=(1 2) 'this is true' 'this is false')
171'this is false'
172```
174### Lines 12-34
176Now let's quickly walk through this code line-by-line. Lines
17712-34 are wrapped in a `|%` (pronounced 'bar cen'), which
178produces a core, a fundamental datatype in hoon similar to a
179struct, class, or object. A core is just a map of names
180to any kind of code, whether it be functions or data. Each
181element in this map begins with a `++` followed by the name and
182the corresponding code. Since `|%` takes an arbitrary number of
183children, it needs to be closed with a `--`.
185<blockquote class="blockquote">
186`++` is not technically a rune, since it is only used in core
187syntax as shown above
188</blockquote>
190Let's step into each of the three arms within our core.
192### `++ sum`
194 ++ sum
195 |= a/@
196 (add (five a) (three a))
197 --
199`|=` produces a function, much like a lambda in lisp. It takes two children:
201- A set of argument(s). In this case our argument set only
202 contains one: `a`, which is required to be an atom or natural
203 number, denoted by `@`.
205- The body of the function itself, which is executed when the
206 function is called (in this case, with `(sum 1.000)`). This
207 particular function adds the results of evaluating the gates `++
208 five` and `++three` with each of their respective input
209 parameters set to `a`.
211### ++ three
213 ++ three
214 |= a/@
215 =| b/@
216 |- ^- @u
217 ?: (lth a b)
218 0
219 (add b $(b (add 3 b)))
221As above, `++three` takes an integer argument, `a`, and then
222executes the remainder of the code with `a` set to the actual
223arguments.
225Similarly, `=|` pushes its first child, `b` into our context (in
226other words, it declares a variable `b`) and executes the
227remainder of the code. However, `b` is not an argument; `=|`
228sets `b` to the default value of whatever type it is declared as.
229Since the default value of an atom is `0`, b is set to `0`.
231So now we have two variables: `a` is set to our input, and `b` is
232initialized to `0`.
234The easiest way to think about `|-` that it lays down a recursion
235point. More on this later.
237`^-` is just a cast that sets the result of the remainder of the
238code to an unsigned integer, `@u`.
240In pseudocode, the last three lines read like this: if `a` is
241less than `b`, produce zero. Else, add `b` to the result of
242rerunning the segment of the function following the `|-` with the
243value of `b` changed to `b` plus three.
245The only thing that should look completely unfamiliar to you here
246is the `$(b (add 3 b))`, which causes us to recurse back to our
247last recursion point with the value of `b` set to `(add 3 b)`.
248Note that we only specify what changes (`b` in this case). If
249you recurse by an actual function call, then you have to specify
250every argument.
252<blockquote class="blockquote">
253If you're familiar with Clojure, `|-` is `loop` and `$()` is
254recur.
255</blockquote>
257**Exercises**:
259Please tweak your code to complete the following excercises.
261There are a few runes and some syntaxes that we have yet to cover that
262you will need to complete the excercises below. For these, please
263refer to our cheatsheat at the bottom.
265- Read and understand `++five` line by line.
267- Change `++sum` to accept two variables, `a` and `b`. Pass `a`
268 to three and `b` to five. Then run the code with `a` set to
269 `1.000` and ` q` set to `2.000`.
271- Check if this new result is under one thousand. If it is,
272 return the string 'result is less than one thousand'. If not,
273 return 'result is greater than or equal to one thousand'.
275```
276Review
278|% start core (collection of named ++ arms; an "object")
279|= define function
280=| define variable from type with default value
281|- drop a recursion point
282^- cast
283?: if-then-else
284=(a b) test equality
285(function args ...) call function
287New material
289- There are two syntaxes for writing Hoon: tall form and wide
290 form.
292 In tall form, expressions are formed with either two spaces or
293 a line break separating both a rune from its children and each
294 of its children from one another. We use tall form when writing
295 multiline expressions.
297 For more concise expressions, we use wideform, which is always
298 a single line. Wideform can be used inside tall form
299 expressions, but not vice versa.
301 Wideform expressions are formed with a rune followed by ()
302 containing its children, all of which are separated by a
303 single space. For example to make a cell of two elements:
305 :-(a b)
307 We've already seen wideform in action, for example with
308 =((mod b 3) 0). In this case = is actually an irregular form
309 of .=, which tests its two children for equality.
311 Surrounding a function with () is an irregular wide form
312 syntax for calling a function with n arguments. More on this later.
314- :- makes a cell of values. The irregular wide form of this is
315 [a b], with two expressions separated by a single space. (While the regular form of this rune takes a fixed number of children--2--its irregular wide form can accept n expressions:[a1..an])
317- Cords are one datatype for text in hoon. They're just a big
318 atom formed from adjacent unicode bytes -- a "c string". To
319 produce a cord enclose text within single quotes. To set the type
320 of an argument to a cord, use @t.
322```