Rootspring
Rootspring
> > @radiantgurl @khvzak Have integrated this PR into my general PR for yielding and luau continuations (which go together anyways as you cant use continuations really without the yielding):...
@khvzak I fixed it slightly with https://github.com/mlua-rs/mlua/pull/593 BTW, it passes all tests at least
Upon further thought, I think just exposing strong count would solve this issue entirely (the debug process at least would be solved)
Is there any update here regarding a close and/or strong count API
> Well, what coroutine.xresume does is rethrow the error, but what you're describing sounds more like a wrapper for pcall? I meant it for C side/embedder use-cases. Its very useful...
> int status = lua_resume(coro, L, 1, &nres); > if (status != LUA_OK && status != LUA_YIELD) > { > std::cout > > > > Ah hmmm... the thing lua_resumeerror...
> Well, lucky for you, that is literally what `coroutine.resume` does: > > static int luaB_coresume (lua_State *L) { > lua_State *co = getco(L); > int r; > r =...
> Yes, you can't resume the coroutine, but you can xmove the error message from the coroutine to the main thread and continue execution there. Just take a look at...
> Looks good so far, we just need to fix some issues that appeared in the snapshot and fix some oversights. > > It's mostly just avoiding trivia being included...
This is a mlua change to block collectgarbage collect etc in sandboxed mode (Im actually the person who asked for this change too) due to the security implications of allowing...