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
{{ message }}
This repository has been archived by the owner on Aug 17, 2022. It is now read-only.
This proposal suggests adding a 'host bindings' section to a warm module.
I do not support this idea. The basic reason is that we already have a mechanism for importing and host bindings are simply a particular kind of import.
More generally, this appears to violate the separation of concerns architectural principle.
Fundamentally, we do need a way of layering multiple semantics over the core machine level semantics of wasm. But that is a separate topic ...
The text was updated successfully, but these errors were encountered:
The current Proposal.md isn't clearly worded atm, so I understand how it's hard to tell what's being proposed. However, Host Bindings aren't an alternative to imports/exports. Coincidentally, I just wrote a comment explaining what, with reference types factored out, are the remaining problems that Host Bindings can help solve.
This proposal suggests adding a 'host bindings' section to a warm module.
I do not support this idea. The basic reason is that we already have a mechanism for importing and host bindings are simply a particular kind of import.
More generally, this appears to violate the separation of concerns architectural principle.
Fundamentally, we do need a way of layering multiple semantics over the core machine level semantics of wasm. But that is a separate topic ...
The text was updated successfully, but these errors were encountered: