You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project is based on an older, but simpler way of building a js toolchain. We are statically compiling everything we need into one wasm file though a series of steps.
When javy switched hands to the bytecode alliance, they moved to a model of linking at runtime. Switching to this model could provide us some benefits. We've already effectively created a poor-man's linker to get exports to work. Supporting host functions would take us deeper down that path. So we either need to make use of a compile time linker or leverage wasmtimes runtime linker. We need some more research before we make a decision. One concern would be supporting other non-wasmtime runtimes. Will it work?
The text was updated successfully, but these errors were encountered:
This project is based on an older, but simpler way of building a js toolchain. We are statically compiling everything we need into one wasm file though a series of steps.
When javy switched hands to the bytecode alliance, they moved to a model of linking at runtime. Switching to this model could provide us some benefits. We've already effectively created a poor-man's linker to get exports to work. Supporting host functions would take us deeper down that path. So we either need to make use of a compile time linker or leverage wasmtimes runtime linker. We need some more research before we make a decision. One concern would be supporting other non-wasmtime runtimes. Will it work?
The text was updated successfully, but these errors were encountered: