mlua VS lua-lockbox

I'm not a specialist about text based multiplayer game, but from what I saw on Wikipedia it seem doable to do it with Rust and Bevy. On top of that you can add a layer of LUA with https://github.com/khvzak/mlua (or write your own bindings and sandbox later).

You can also look at the "dependents" section on crates.io https://crates.io/crates/mlua/reverse_dependencies and github https://github.com/khvzak/mlua/network/dependents

Note rlua doesn't allow you to create native modules with it and has largely been superseded by https://github.com/khvzak/mlua since it's more maintained, has native module support and stuff like Luau and async/await.

I'm glad to announce first mlua version 0.8.0-beta.1 with Roblox Luau support.

I believe mlua [0] is the recommended Lua Rust binding now.

[0] https://github.com/khvzak/mlua

This is achieved through a backend/client architecture -- all core functionality (getting query results, opening selected item, search engine fallback, etc.) is implemented in a "backend" module, which is a Rust library exposed as a Lua module via mlua. The results returned by the backend then get fed into your fuzzy-finder of choice through thin clients, or "providers".

Enter the newest iteration: native Rust bindings to Lua! Instead of communicating with the Rust backend through a Plenary job. the Rust backend now directly exposes a Lua API using the excellent mlua library which provides high-level Rust bindings to Lua. This allows me to basically implement a Lua module in Rust, so while the backend is written in Rust, you can directly import it as a Lua module (e.g. require('libdash_nvim').query()).

I really love mlua. The api is excellent. You can convert between Rust and Lua values either with the ToLua and FromLua traits, and also serde serialization/deserialization. I tend to use a little of both.

Lua is able to call back between C and Lua, just like Python. Rust wrappers/implementations like mlua exist to make this possible between Rust and Lua too.

With my recent foray into Lua programming, and seeing just how many pure Lua modules there are for some tasks (like lua-lockbox for crypto primitives), and the fact LuaJIT can interface pretty easily with any C ABI, I've definitely considered it, especially since I could modify existing software to shove a Lua interpreter in for my needs.