msgpack-rust VS rlua

This is similar in practice to using abi_stable, and end-users will still receive compiled files, but your plugins will be sandboxed and a single build will work on all platforms. The downside is that it's a bit more work because WebAssembly's support for passing complex data types between the host and the WebAssembly code is in the preliminary stages, so you need to do something like using Serde to encode your data into something like Bincode or MessagePack (or JSON and friends) to hand it off between the host and the plugin.

There's the rlua package for running lua in your rust app: https://github.com/amethyst/rlua

Some sys crates do embed the source files, like rlua for example.

[1] - https://github.com/amethyst/rlua/blob/master/examples/guided_tour.rs

Yes though, given that a CCleaner/BleachBit-style situation is going to be I/O-bound, I'd probably go with rlua, PyO3, or rust-cpython for plugins.

I wrote up some rust low-level bindings for guile [1]. The problem is that Guile liberally uses setjmp/longjmp, which breaks rust destructors. It might be possible to fix this by wrapping every call the way rlua does [2], but I'm not familiar enough with Guile to know.

1: https://github.com/ysimonson/guile-sys

2: https://github.com/amethyst/rlua/issues/21

And.. another binding finally called rlua https://github.com/amethyst/rlua

hlua or rlua are what you want for Lua, rust-cpython or PyO3 for Python, rutie for Ruby, and possibly deno_core for JavaScript.

Janet is what introduced me to Fennel. Conjure [1] sold me on Fennel over Janet. The Neovim community is rallying around Lua.

(And in fact, what sold me on Rust was its truly excellent Lua FFI support [2].)

[1]: https://github.com/Olical/conjure

[2]: https://github.com/amethyst/rlua