Brian Maher

@ImagicTheCat can you answer this question? How are you getting data from one Lua VM to the other?

As mentioned in the PR, I'm happy to accept the contribution that supports the send API (and the Async constant export), and maybe documentation on how to do the rest...

The only safe way I can think of to do this is to have memory stored *outside* of the Lua VM which contains the loops and async watchers which are...

Thank you for the contribution. I added a general disclaimer about using the FFI approach along with a suggestion on how we could safely implement this if someone wants to...

It appears that `brew install libzip` is not installing zipconf.h. A quick fix for you is to run these commands: ``` cp /usr/local/Cellar/libzip/1.2.0/lib/libzip/include/zipconf.h /usr/local/Cellar/libzip/1.2.0/include/zipconf.h ln -sf ../Cellar/libzip/1.2.0/include/zipconf.h /usr/local/include/zipconf.h ``` ...a...

Sorry, I completely lost track of this pull request :(. I like the idea of using Markdown for documentation, but I'm not sure that this documentation is any better since...

I'm a little confused here... This rock should be creating a zlib.dll which is on your LUA_CPATH and NOT on your PATH, so there should not be a naming collision...

Maybe because we use the old `luaL_register` function when we should be using `luaL_setfuncs`? https://github.com/brimworks/lua-zlib/blob/master/lua_zlib.c#L1263 Feel free to issue a pull request if this change fixes your issue. Thanks! -Brian

Perhaps a little "macro magic" could solve this problem? Pull requests are welcomed :).

I see two warnings... what is the failure?