mlua VS nvim-rs

The release notes can be found here.

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).

mlua can run on emscripten target with Luau backend -> https://github.com/khvzak/mlua/issues/23

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

I know mlua does support Async. I also prefer it over rlua

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".

Nvim-rs is a rust library for writing rpc clients for neovim, utilizing the async/await language feature. It allows to write guis that embed neovim (like neovide and gnvim), external clients (like nvim-send), or more standard plugins (like this port of the iconic scorched earth).

2) Not sure, did you see the examples and the docs on them (note there's a submodule with documentation for some of them)? Can you be a bit more specific on what's missing? It is true however that I left integrating the plugin into neovim to a reference to the original scorched earth. I think you're right that I should integrate that into the examples documentation, thanks for pointing that out!

This is really cool. I am in the early stages of trying to do something similar. I've been building atop https://github.com/KillTheMule/nvim-rs where neovim sends rpc calls to a rust async runtime. Is that similar to how things were done in your previous iteration?

I guess this: