mlua VS crates.io

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

So, be sure to double-check your critical libraries and be sure their alternatives exist in the Rust ecosystem. There’s a good chance the crates you need are available in Rust's crates.io repository.

The previous section was very simple, this section is also very simple but introduces us to cargo which is Rust's package manager, as a JS dev my mind goes straight to NPM.

Now, there has to be a place where all these packages come from. Similar to npmjs registry, where all node packages are registered, stored and retrieved, Rust also has something called crates.io where many helpful packages and dependencies are registered.

Before proceeding, let's check https://crates.io/, the official Rust package registry.

The most thrilling aspect has been the joy of writing the backend. It's like every struct, enum, and method in Rust forms this interconnected Multiverse of code , which you can see in crates.io which is best Documentation experience I Ever Had.

5. Crates.io

When using crates from eg. crates.io, and also things like std and core

Vendoring your packages was very tedious to even remotely get to work with Cargo. I spent a very long time getting Cargo to work together with cargo-local-registry. We vendor crates from crates.io and a custom internal registry.

So this is my question: Which way was the right to find it out? There is no info about this feature on crates.io. I also have no clue what exactly it does and why it is named rwh_05.

Rust does it so much better with https://crates.io . I don't know why Go can't (or won't) do something similar.