Sigilante

https://gist.github.com/sigilante/5c9f38efb52fb256649059158a98c2f3 Update here. @joemfb @tacryt-socryp I had a good chat with @joemfb this morning. We have three options now: 1 .Userspace-first. Ship it in /lib. Don't worry about direct atom...

Current status: I have moved things over to `%zuse`. I have upgraded the unit tests. I would still like to move some parsing/printing functions over into `++la`, and possibly introduce...

@joemfb gonna call this one ready for serious consideration to be complete now.

Yeah, we're all agreed it's a metadata bit/byte. - `1` single bit as head tag, use `++met` in `++length`; advantage: no 2^31 length limit - vector length as head tag,...

Head pin of `1` is dimensionality for the vector library, it's true.

The change was trivial, only in `++zeroes` and `++length`. Since nothing is done with that pinned value (or even multiple values at the head), setting up a more sophisticated type...

@joemfb accounting for jet matching is it likely that a jetted C version of the get/set routines would actually be faster? (Currently it's done with bit masks etc. in Hoon.)

I added the `++cumsum` function and a `++subvector` tool as well.

This should synchronize @lvs and @lvd entirely, no equivalent forms.

There are five issues to resolve: - [x] `++expect-eq` isn't adequate for floating-point maths so I'll need to write an `++expect-close` - [x] The empty vector is `0x1` not `0x0`...