Sigilante

The current test status: ``` OK /lib/lv/test-zeros OK /lib/lv/test-unmake OK /lib/lv/test-sum OK /lib/lv/test-subv OK /lib/lv/test-subs OK /lib/lv/test-set OK /lib/lv/test-product OK /lib/lv/test-ones OK /lib/lv/test-mulv OK /lib/lv/test-muls OK /lib/lv/test-max OK /lib/lv/test-make-unmake OK...

Currently getting a build error around something that works locally... `++all-close` checks all members of two vectors for `++isclose`, but the testing suite blocks the build because of an atom...

I wrote an `++expect-near` to handle closeness of floats. ```hoon ++ expect-near |= [expected=vase actual=vase] ^- tang :: =| result=tang :: =? result !(all-close:lvs `@lvs`q.expected `@lvs`q.actual .1e-6) %+ weld result...

OK, here's the last one: ``` > !>(%.y) [#t/%.y q=0] > !>((isclose .1 .1.00001 .0.0001)) [#t/?(%.y %.n) q=0] > (isclose .1 .1.00001 .0.0001) %.y ``` `++isclose` is picked up by...

Shunting forwards discussion: - [x] Resolve loobean match (previous comment). - [x] Write the `@lvd` tests, which are straightforward, pending loobean test fix. On that basis, this Hoon is ready...

With that resolved, I need to bring in the `@lvd` tests, then this PR is "done" or at least ready for the next phase.

Done with `@lvd`, and that's a Highday night. HMU when you're ready to take this to the next step, figuring out where in `%zuse` or `%lull` to house it or...

@joemfb I'm going to pull the jets together. They're pretty much all written---actually, I'm going to cut some out---but should I work on a %zuse-compatible refactor of this so the...

@joemfb this one is still flagging a requested change but I can't figure out which it would be. (I think I outdated it but not sure.)

Opening for comment. We actually don't want this as a `/lib`, if we want it then we want them in `/sys/hoon` next to their sources.