source-academy / py-slang / 29805324553

86%

push

github

WASM engine: conductor module loading (from X import y) (#283)

* WIP: wasm runtime HOSTREF tag + dispatch (to be amended)

* WASM engine: conductor module loading (from X import y)

Completes the module-import pathway started in aa00a6a (HOSTREF runtime
tag + dispatch):

- moduleInterop.ts (new): conversion layer between the WASM engine's
  tagged (i32, i64) runtime values and the conductor module protocol's
  TypedValues — the WASM analogue of pvml/modules.ts. Async IDataHandler
  traversal happens up front (prepareModuleBindings, at import-load
  time); materialisation into wasm values happens synchronously via the
  instance's own make* exports when the compiled FromImport executes,
  respecting the shadow-stack GC discipline.
- builderGenerator.ts: modules.get / modules.call host imports
  (declared unconditionally, like every other host import); FromImport
  compiles to one modules.get + SET_LEX_ADDR store per bound name;
  FromImport names participate in scope scanning; dataEnd exposed so
  the host can read string arguments.
- hostImports.ts: log_hostref console import for print()ing imported
  module values.
- index.ts: wire the modules import namespace into compileToWasmAndRun.
  modules.call is async on the JS side, so it is wrapped in JSPI
  Suspending (and main entered through `promising`) when both module
  bindings and JSPI are present; without JSPI, imported module values
  still work but calling a module function raises a clear error.
  Without bindings, loud stubs preserve the uniform import shape.
- compiler.ts/types.ts: thread CompileOptions.moduleBindings and the
  dataEnd boundary through compilation.

Evaluator-side loading (PyWasmEvaluator collecting a chunk's imports
into PreparedModuleBindings before compilation) is the remaining piece.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FbExZBaxgeUL4oi1t7PG93

* Finish PyWasmEvaluator module-loading integration; fix Gemini... (continued)

4279 of 5352 branches covered (79.95%)

Branch coverage included in aggregate %.

106 of 183 new or added lines in 8 files covered. (57.92%)

9281 of 10403 relevant lines covered (89.21%)

178866.87 hits per line