From 6f8ba7c7b7e7c26bd5d99a06eb128be823d2bc61 Mon Sep 17 00:00:00 2001 From: Kingdon Barrett Date: Sun, 24 Aug 2014 16:56:23 +0000 Subject: [PATCH] nowhere near enough / typos Looks like a 'the' was omitted too --- doc/hoon/tut/6.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/hoon/tut/6.md b/doc/hoon/tut/6.md index 182b7ba..aefce55 100644 --- a/doc/hoon/tut/6.md +++ b/doc/hoon/tut/6.md @@ -940,7 +940,7 @@ first item in `a`, selected via the `++snag` function: `++snag` of course selects any item in the list; but if `b` has a type more complex than a homogeneous list (eg, the type system might well know the number of items, etc, etc), Hoon is nowhere -near enough to see that the counter is always 0. So the type +near smart enough to see that the counter is always 0. So the type produced by `++snag` is the union of all list elements, which is precisely the type we want for our homogenized list. @@ -955,7 +955,7 @@ As for `^.` (`ketdot`, `%ktdt`), we can see it in `++open`: Ie, `^.(a b)` is `^+((a b) b)` is `^-(_(a b) b)`. `++weld` prudently casts its product to the type of the base list -`b`. In future this `^+` will probably be removed, since we are +`b`. In the future this `^+` will probably be removed, since we are perfectly capable of inferring that when you weld `(list a)` and `(list b)`, you get a `(list ?(a b))`. But there's old code this change might confuse.