Tim Caswell

Right, that would work. `uv.argv()` that returns an array of strings would work well. I don't have any idea how we would pull the argv our of libuv though. I...

Looking through libuv, I don't think they store the full argv, but we could store a copy in our bindings to uv_setup_args somewhere.

I like the global stash idea. Do whatever you think is best. My only preference is to diverge from libuv as little as possible.

The module knows it's full path. It's __filename, and __dirname from within the module. Is this all that's needed or are there cyclic require dependencies as well.

I don't think I can change the signature of the C interface to addons, but you could wrap the module in a lua script which then requires the native addon...

As long as the C module has a way to pass in the needed values via lua arguments, it's trivial to write a lua shim. The shim script would know...

Regarding spec for base 8, I gave this some thought. For bases that evenly break bytes into characters, pad to full bytes, this is base 2 (8 chars), base 4...

I wrote a base-8 codec that works similar to base-32 and base-64 where you give it an alphabet and an optional padding character. https://github.com/filecoin-project/lua-filecoin/blob/master/base-8.lua For example base8 with `'01234567='` as...

I've not seen any others. I don't know if there is a common encoding for this. Logically, the same style as base-64 and base-32 makes the most sense.

Personally I see base-2 and base-8 both as unneeded. Is there any use case where they are the correct solution? Base-16 works everywhere and encodes much shorter and easier than...