luau

It’s designed for *standard Luau*, so it works anywhere Luau runs — not just inside Roblox projects.

The engine is written in C++ and uses Luau (Roblox's Lua fork) as the sandboxed scripting runtime.

Also it looks like[1] Luau is the official Roblox Studio scripting language, and is baed on Lua 5.1 (possibly LuaJIT?) which means it's behind mainstream Lua.

Overview This model is built on Qwen2.5-Coder-1.5B-Instruct and has been fine-tuned exclusively on the official Roblox Luau corpus.

And you don't really need to know Luau to use xllify: the AI writes it for you.

Plus if you stay on 5.1 you get compatibility with LuaJit and Luau so much better performance.

It is designed to assist developers with code generation, completion, and understanding of Luau patterns commonly used in Roblox game development.

Is each instance of a game executed in a docker container, and the luau code isolated that way or is there some multi-tenant solution?

Number literal enums degrade to `number` because Luau can’t express them.

Anyway, the same Luau code runs two ways:..

> Astra is a web server runtime for Lua (5.1-5.4), Luau and LuaJIT written in Rust with native support for Teal.

I know Luau is perhaps a left-field choice.

The first sentence in its readme is the following: "Astra is a web server runtime for Lua (5.1-5.4), Luau and LuaJIT written in Rust with native support for Teal."

I used Luau with the -g0 -O2 --codegen options (didn't add --!native to the code though), which according to my understanding automatically selects the "profitable" functions for native compilation.

Luau coroutines are supported, so functions can do non-blocking work (API calls, streaming data) without locking up the calculation chain.

Luau in interpreter mode is pretty much as fast as LuaJIT 2.1 in interpreter mode.

Luau with (partial) native compilation is factor 1.6 slower than LuaJIT 2.1 in JIT mode.