f48e96c · urbit.org · git.iko.soy

git.iko.soy/urbit.org

fixes highlights

commitf48e96c62dc916e22aebad28a2029750a06ffbbb authorsyzygyzer <jon@tlon.io> dateTue 22 Oct 2019, 13:06 (7 years ago) parent1e117b2

2 files changed+3−3

compare with master

unifiedsplit

tutorials/hoon/ford.md+1−1 tutorials/hoon/test-sets.md+2−2

tutorials/hoon/ford.md+1−1

@@ -100,7 +100,7 @@ Now that we have covered the distinctive features of Ford, we now dive into some

100100#### Vase

101101

102102From `hoon.hoon`:

103−```

103+```hoon

104104+$ vase [p=type q=*]

105105```

106106A `vase` is simply typed data, and it is used wherever typed data is being explicitly worked with.

tutorials/hoon/test-sets.md+2−2

@@ -13,7 +13,7 @@ First we will cover the essential molds, arms, and generators used for testing,

1313## Running our first test

1414

1515To start with, lets try running the unit tests on sets by entering the following into the Dojo, and then we will work backwards to see how we obtained this output:

16−```hoon

16+```

1717> +test /sys/hoon/set

1818OK /sys/hoon/set/test-set-all

1919OK /sys/hoon/set/test-set-any

@@ -173,7 +173,7 @@ When we ran the command `+test /sys/hoon/set` in the Dojo, what ultimately happe

173173

174174In other words, if you want to run all of the tests located in `/tests/sys/hoon/`, you would run `+test /sys/hoon`:

175175

176−```hoon

176+```

177177> +test /sys/hoon

178178OK /sys/hoon/auras/test-parse-p

179179OK /sys/hoon/auras/test-parse-q