I noticed that you snagged a couple names on crates.io as well, so I came to take a look at what you were working on.

I'm opening this issue to help track the addition of an API that can be used from Safe Rust. My crate has an example of what using Luau from Safe Rust might look like; it compiles and runs but that's about all the functionality that's implemented right now:

use std::ffi::CStr;

use luau::vm::{Luau, StackValue, Value};

fn main() {
	let vm = Luau::new().expect("failed to create Luau VM");
	let compiled = Luau::compile("return ...")
		.expect("failed to compile function");

	let chunkname = CStr::from_bytes_with_nul(b"=basic_run.luau\0").expect("die");
	let main_thread = vm.main_thread();
	let function = main_thread.load_compiled(compiled, chunkname)
		.expect("failed to load function");

	println!("{:?}", function.call_sync([
		Value::new_string(&main_thread, "hello world").unwrap(),
		Value::new_string(&main_thread, "I like trains").unwrap(),
		Value::new_string(&main_thread, "how about a table?").unwrap(),
		Value::new_table(&main_thread, 0, 0).unwrap(),
		Value::new_string(&main_thread, "I like trains").unwrap()
	]));

	// assert stack usage is balanced
	assert_eq!(unsafe { StackValue::stack(main_thread.as_ptr()) }, Vec::new());
}

If you can manage to get autocxx to generate bindings to the high-level C++ magic like analysis and AST, your crate could pretty quickly speed ahead of mine in the compilation/analysis department, since I'm focusing on VM right now. Different versions of Luau can't be mixed in the same application (or else linking errors result), so I've just added a feature to my crate that allows users to disable compilation and linking to Luau so that people have the choice to use your crate as the compiler if they so choose.

Good luck and may the best crate win! :)

Hello, I'm mlua author and currently working on adding Luau support to it. I see you registered a few crates on crates.io and curious do you have any plans to support the rluau in future? I'm asking because created a new dependency for mlua named luau-src, similar to lua-src and luajit-src that I maintain. But seems the name luau-src is already taken so if you don't have future plans for rluau, can I kindly ask to transfer ownership of luau-src to myself? Or I will register another name.

PS I already added initial Luau support to the mlua on dev branch.

Use autocxx. Library is in a usable state now. Would prefer to move most of these bindings to raw externs where possible like the lua* api so you don't need useless struct wrappers that autocxx forces