Repository navigation
Tracking issue for deferred evaluation integration #101
Description
When we rebase to the spec for deferred evaluation, the ESM integration should be updated to conform to the late execution semantics.
There are two aspects to the integration here:
- WebAssembly itself can be imported as a deferred namespace (
import defer * as ns from './mod.wasm'). This was already designed for previously when we switched to synchronous instantiation, so gets supported naturally. - When WebAssembly imports from JavaScript or other WebAssembly that supports deferred evaluation, whether WebAssembly itself would want to be able to defer evaluation.
While (1) we get "for free", (2) would require some design work.
In particular, WebAssembly would need a way to (a) define an import phase, and (b) obtain a JS module namespace object import. A proposal for this is outlined in #119.
Activity
nicolo-ribaudo commentedon Feb 13, 2025
Is there anything we actually need to do?
guybedford commentedon Feb 13, 2025
Nothing right now, mainly I just wanted a tracking issue to note that this is planned for when the specification is ready to be used.
I suppose in theory we could have a PR already up ready for the rebase, but there's no rush on that.
guybedford commentedon Jul 11, 2025
Following up on this one again - @nicolo-ribaudo is there anything we still need to get here, or do we get this integration naturally in the current spec model?
Rename variables in Overview.md (#101)