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
Hello, I am working through the examples, and I noticed exports-memory does not seem to work if I create it as a standalone project.
|
1 | use wasmer::{imports, wat2wasm, Instance, Module, Store, TypedFunction, WasmPtr};
| ^^^^^^^^^^^^^ no `TypedFunction` in the root
If I check out the main wasmer repo and run the example with cargo run --example exported-memory --release --features "cranelift" it works just fine.
I wonder if when the NativeFunc -> TypedFunctionrename occurred, the examples got updated as well, but the 2.3.0 version of wasmer does not support the new TypedFunction yet (I think this may occur with a few other examples as well)?
I wonder if when the NativeFunc -> TypedFunction #2939 occurred, the examples got updated as well, but the 2.3.0 version of wasmer does not support the new TypedFunction yet (I think this may occur with a few other examples as well)?
Looking at the list of changed files, I'd say breaking changes happened in nearly all the examples.
Thanks for repoting the issue. The current examples have changed from the 2.3.0 API so that's why you are encountering the issue.
If you use the file from the 2.3.0 tag things should work properly. Sorry for the confussion, as soon as we release the Wasmer 3.0 beta it should be solved.
Summary
Hello, I am working through the examples, and I noticed
exports-memory
does not seem to work if I create it as a standalone project.If I check out the main
wasmer
repo and run the example withcargo run --example exported-memory --release --features "cranelift"
it works just fine.I wonder if when the
NativeFunc
->TypedFunction
rename occurred, the examples got updated as well, but the 2.3.0 version of wasmer does not support the newTypedFunction
yet (I think this may occur with a few other examples as well)?Repro & Logs
cargo run
: https://gist.github.com/kmott/52eb2e3ba13431d8737e604f13d8fee0The text was updated successfully, but these errors were encountered: