Closed rjzak closed 2 years ago
Sure.
The absence of symmetric_state_clone()
may still be an issue, though.
Does wasmtime
compile without this being implemented?
v0.1.6 has been uploaded to crates.io
.
@jedisct1 I have a PR for Wasmtime where clone throws a not implemented error. https://github.com/bytecodealliance/wasmtime/pull/4612/files#diff-91afb02a17fcb6af253b7333ddcc5f2a14cc46313fb7a8527b78f3922d521b5b
You mentioned before that you had code but it wasn't working. Could we work on that together? With the references, and learning about witx, I haven't been able to get it working properly.
Ideally, that function should be implemented in the wasi-crypto
crate, even if it returns NotImplemented
.
For some reason, wasmtime-wasi-crypto
also generates code from the Witx files, including the code which glues wasi-crypto
to the Wasmtime exec. That should also be moved to wasi-crypto
I think, but I haven't been able to get my head around Witx and how the generated code connects to everything else. Also, isn't there an effort or goal to move Witx to Wit? Not sure how that changes things.
The wasi-crypto
crate can be reused across runtimes, while the wasmtime-wasi-crypto
contains the wasmtime specific bits.
The witx
file is required so that wasmtime
can link all the functions. And wiggle
generates prototypes (well... "traits") from witx
files to make sure that they are implemented.
Using WIT is going to be necessary, but will require a ton of work, as with WIT comes a new ABI and new tools that are still WIP or existing tools that have to be updated.
Could we have a new release so that Wasmtime may pull it in from crates.io?
Refs: https://github.com/bytecodealliance/wasmtime/pull/4612