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 Jan 2, 2024. It is now read-only.
It would very convenient to a builder object for the execution context -- this would allow importers to choose which host imports to use when instantiating a specific engine -- and it would make it much clearer what host imports are available.
Currently, core WASI, experimental HTTP, and WASI NN are imported by default -- the default should probably just be core WASI, with the other options (and as we add more) available through the builder.
The builder will probably have to contain references to the store and linker used for pre-instantiation.
This could also be a good exercise in thinking about allowing implementers to define their own host imports.
The text was updated successfully, but these errors were encountered:
It would very convenient to a builder object for the execution context -- this would allow importers to choose which host imports to use when instantiating a specific engine -- and it would make it much clearer what host imports are available.
Currently, core WASI, experimental HTTP, and WASI NN are imported by default -- the default should probably just be core WASI, with the other options (and as we add more) available through the builder.
The builder will probably have to contain references to the store and linker used for pre-instantiation.
This could also be a good exercise in thinking about allowing implementers to define their own host imports.
The text was updated successfully, but these errors were encountered: