Luke Gorrie

Do I understand correctly that this is essentially a feature to cast a Lua object to an FFI pointer and back again? If so then I think this would be...

Let me see if I am following this correctly: You are adding primitives to cast Lua object/value references back and forth to 64-bit numbers; You need to implement this separately...

@alendit Maybe a bit more background feedback to the patch you posted above... The intention of this code seems to be to capture the pointer-value of the Lua object at...

One other thought, mind wandering ahead a bit... You have a few options for how you can represent your handle. 64-bit integer has the upside that it can encode any...

Great hacking :) interested to hear how it all progresses.

> Right now I works with the caveat that from_handle can't determine which type it loads. I look into it next. Could look for inspiration in `sload`. This instruction loads...

> A time-traveling debugger like mozilla rr help a lot to figure out what's going on. I need to step up my game with gdb/rr. The next major dev I...

> Right now that CNEWI allocation seems to not to be eliminated, even though it totally could, IMHO. Braindump: `CNEWI` gets eliminated by the "allocation sinking" optimization. This optimization will...

The FFI is limited to defining max 64K types. Each time you call `ffi.typeof("struct ...")` you are creating at least one new type (and possibly more for pointers and references.)...

Just remember that every time you call `ffi.typeof("struct ...")` you will define a new C type, even if the structure definition is the same. So if you only need one...