Skip to content

docs: clarify supported wasm scope #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
CheckPickerUpper wants to merge 1 commit into from
Closed

docs: clarify supported wasm scope #60

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 12 additions & 9 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,23 +100,26 @@ ready.

## Current scope

Supported: the full core wasm instruction set — numeric ops (i32/i64/f32/f64),
Supported: the currently translated core wasm subset — numeric ops
(i32/i64/f32/f64),
comparisons, conversions, locals, globals, memory load/store, **bulk memory
(copy/fill/init + passive data segments)**, `call` / `call_indirect`,
(copy/fill/init)**, active and passive data segments, `call` / `call_indirect`,
`block` / `loop` / `if` / `br` / `br_table`, `select`, `memory.grow`, data
segments, element segments, start function, exports, function imports.

The bundled `runtime/roblox.luau` provides a handle-based Roblox binding layer
(get service, instance creation, number + Vector3 properties, print, destroy),
tested against a mock Roblox environment.

Rejected loudly (typed reasons): SIMD (`v128`), atomics, memory imports,
exception tags, shared/64-bit memories, table/global exports, and
passive/declarative element segments.
Rejected loudly (typed reasons): SIMD (`v128`), atomics,
exception-handling tags, shared or 64-bit memories, multiple memories,
non-function imports, global/table/tag exports, and passive/declarative element
segments. Passive **data** segments are supported
through `memory.init`; passive element segments are not.

Documented approximations: `i64` values are represented as Luau numbers and
are exact only through 53 bits; some i64 operations currently reuse 32-bit
helper paths. `f32` rounding is not modeled, and division-by-zero does not
trap.
Documented approximations: `i64` values are represented as Luau numbers, so
values above the exact-integer range of IEEE-754 doubles are rounded; several
operations currently reuse 32-bit helper paths. `f32` rounding is not modeled,
and division-by-zero does not trap.

See `CLAUDE.md` for the full architecture and agent guidance.
Loading