Tim Stableford

I think the lua_xmove is the memory leak in callByteCode. I can't remember why it's that way though. I have a suspicion something about returning a function from doString and...

@ParadiseFallen I've come up with something that might make this more palatable (to me, I can't speak for @ceifa who will be merging it). What you could do is overload...

You're right that you proposed a return mode, which I generally liked but the explicit return type of multireturn I think will make it easier. I've just been reading through...

For JS interoperability unless I'm misunderstanding you. Consider exposing the JSON.stringify function to Lua as an example. So Lua does ```lua JSON.stringify({}, function (replacer) return something end) ``` stringify expects...

Sorry @ParadiseFallen I'm not following the problem you're describing. Currently the example I showed works and I'm not sure what your function is showing

Hi @janfrodej When I PR'd adding the null type I wanted to have it distinct from nil because nil is equivalent to undefined in JS. This stemmed from a need...

I've put some comments on his PR and I think overall he has a fair point but I'm not certain on the implementation