magus-utils

Overview ¶

Subcommand `moduleset` emits internal/interp/bindings/gen's module registry: the table mapping each host module's bind name to its generated Register trampoline.

It emits TWO files because the registry is build-tagged. modules.go is the native set and references every trampoline including the IO ones; modules_wasm.go is the browser playground's subset and must not, so the wasm build sees a parallel table.

Both were hand-maintained, and the wasm half carried the instruction "Keep this in sync with the WASM-capable entries of modules.go" - a mirror with a rule no test could check, because the WASM classification lived nowhere but in those two tables. std.Module.WASM now declares it, which is what makes both files projections.