rqio run / build / repl

rqio run

Execute RayQuiro scripts directly using the high-performance Bytecode VM.

rqio run <file.rq> [args...]
rqio run <file.rq> --watch        # Hot Reload: automatically reloads on file save

Hot Reload (--watch / -w)

When the --watch flag is passed, rqio keeps running and continuously monitors the script file. Every time you save changes to the file, the runtime immediately reloads and executes the updated code without restarting your terminal.

rqio run app.rq --watch

Arguments passed after the script path are accessible within RayQuiro via process.args().

---

rqio repl

Launch the interactive RayQuiro REPL (Read-Eval-Print Loop) shell:

rqio repl
rqio           # Running rqio without arguments in a non-project folder also opens REPL

RayQuiro 1.0 features an enhanced console REPL with full line-editing capabilities:

• Up / Down arrows (↑ / ↓): browse command history
• Left / Right arrows (← / →): move the cursor and edit text in-place
• Backspace & Home/End: precise in-line text editing

RayQuiro 1.0 REPL
Type "exit" or press Ctrl+C to quit.

>>> var x = random.int(1, 100)
>>> x * 2
84
>>> fn greet(name) { return "Hello, " + name + "!" }
>>> greet("RayQuiro")
"Hello, RayQuiro!"
>>> exit

---

rqio build

Compile a RayQuiro script into a standalone, bare-metal native binary. The compiled executable has zero external runtime or VM dependencies.

rqio build <file.rq> [-o output] [flags...]

Supported Compilers

RayQuiro 1.0 includes autonomous compiler support:

1. TinyCC (TCC): Bundled directly with RayQuiro (tools/tcc/ on Windows, system tcc on Linux). Enables fast, zero-dependency autonomous native compilation without requiring Clang, LLVM, or GCC installed on the machine.
2. LLVM / Clang: For aggressive compiler optimizations and cross-compilation.

Flags

Flag	Description	Details
-o <path>	Output binary path	Defaults to script name (.exe on Windows, no extension on Linux/macOS)
--tcc	Autonomous TinyCC	Compiles within ~10ms using the bundled TinyCC toolchain (default for normal builds)
--llvm	Clang / LLVM	Compiles via LLVM Clang
--release	Maximum performance	Enables -O3 LLVM optimization passes (falls back to TCC if Clang is unavailable)
--debug	Debug build	Generates -O0 -g debug symbols for GDB / LLDB / VS Code
--target <triple>	Cross-compilation target	Target architecture and OS (e.g. linux-x64, win-x64, wasm32-wasi)
--no-llvm	GCC fallback	Forces compilation using GCC instead of LLVM/Clang

Target Aliases

The --target flag supports shorthand aliases as well as standard LLVM target triples:

Alias	Target Triple	Target OS & Architecture
linux-x64	x86_64-unknown-linux-gnu	Linux 64-bit (x86_64)
linux-arm64	aarch64-unknown-linux-gnu	Linux 64-bit ARM (AArch64)
win-x64, windows-x64	x86_64-pc-windows-gnu	Windows 64-bit (x86_64)
macos-arm64, darwin-arm64	arm64-apple-darwin	macOS Apple Silicon (M1/M2/M3)
macos-x64, darwin-x64	x86_64-apple-darwin	macOS 64-bit Intel
wasm, wasm32, wasm32-wasi	wasm32-wasi	WebAssembly (WASI) bytecode .wasm

Examples

# Autonomous build via TinyCC (no external compiler required)
rqio build app.rq -o app.exe

# Explicitly use TinyCC
rqio build math.rq --tcc -o math.exe

# Maximum release optimization with LLVM
rqio build game.rq --release -o game.exe

# Cross-compile for Linux x86_64
rqio build server.rq --release --target linux-x64 -o server

# Debug build for stepping through with a debugger
rqio build script.rq --debug -o script_debug.exe

---

3. Packaging RayQuiro Binaries (rqio pack)

For custom operating systems and lightweight runtime distributions, RayQuiro supports packaging applications into .rqb bytecode bundles:

rqio pack main.rq -o app.rqb

• Produces a compact standalone binary package with the RQB1 header.
• Can be executed directly with rqio run app.rqb or registered with Linux binfmt_misc for native OS execution.