Wasmtime GitHub notifications bot (Jul 15 2020 at 18:16): Wasmtime GitHub notifications bot (Jul 15 2020 at 18:16):fitzgen opened Issue #2025:
We made changes to the Rust API so that creating a module requires an engine, not a store. However, we didn't propagate this change out to the C API (nor the python API and I assume not to the go or .NET APIs either).
We should do this. It might require using non-standard
wasmtime.hfunctions, unless we convince upstream to make this change as well.
Wasmtime GitHub notifications bot (Jul 15 2020 at 18:16):fitzgen labeled Issue #2025:
We made changes to the Rust API so that creating a module requires an engine, not a store. However, we didn't propagate this change out to the C API (nor the python API and I assume not to the go or .NET APIs either).
We should do this. It might require using non-standard
wasmtime.hfunctions, unless we convince upstream to make this change as well.
Wasmtime GitHub notifications bot (Jul 15 2020 at 18:52):yurydelendik commented on Issue #2025:
We made changes to the Rust API so that creating a module requires an engine, not a store.
Yeah, the reason was
HostRef. Now since it is gone we can change signature ofwasmtime_module_new.
Wasmtime GitHub notifications bot (Jul 15 2020 at 18:54):yurydelendik edited a comment on Issue #2025:
We made changes to the Rust API so that creating a module requires an engine, not a store.
Yeah, the reason was
HostRef. Now since it is gone we can change signature ofwasmtime_module_new.
Wasmtime GitHub notifications bot (Jul 15 2020 at 20:34):fitzgen closed Issue #2025:
We made changes to the Rust API so that creating a module requires an engine, not a store. However, we didn't propagate this change out to the C API (nor the python API and I assume not to the go or .NET APIs either).
We should do this. It might require using non-standard
wasmtime.hfunctions, unless we convince upstream to make this change as well.
Last updated: Dec 23 2024 at 13:07 UTC