Alex Orlenko
Alex Orlenko
Makes sense, I'll add back in 0.10.1 support of wrapped userdata types (probably under a feature flag).
Luau has debug api (`lua_singlestep`) that allow to stop execution after each instruction. mlua does not support yet this api through safe interface, as it's designed for debugging only and...
> there is no way to safely sandbox mlua as any user code which makes and handles too many references can panic and cause issues, especially in a multi tenant...
Could you provide some context please, what problem are you trying to solve? Lua/C continuations are rather workaround to allow suspending C functions. In Rust world this is solved by...
Thank you for the context and explanation. mlua was never designed to support all (especially niche) use cases, and merging PRs with relatively complex code creates a significant long-term maintenance...
I can agree that yielding with arguments can be beneficial in some cases, but it's more complicated problem than it might seem at first glance. A simple example: ```rust let...
~Pluto support added (initial for now, will add sandboxing mode too)~. Reverted
Unfortunately Pluto code quality is not ideal, first pass on CI failed with buffer overflow errors. Currently blocked by https://github.com/PlutoLang/Pluto/pull/1121
There is [`Thread::reset`](https://docs.rs/mlua/latest/mlua/struct.Thread.html#method.reset) with does exactly the same.
> is meant to mimic `coroutine.close`, marking it as finished. I don't think it's mlua goal to replicate functionality of Lua standard library. The idea behind `Thread::reset` is to provide...