Remove Wasmtime dependency from wasmi_wasi
crate
#563
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #561.
Unfortunately
wiggle
version1.0.2
is the most recent version that is Wasm runtime agnostic. All later majorwiggle
versions starting withwiggle
version2.0.0
and up and therefore also all laterwasi-common
version (sincewasi-common
builds on top ofwiggle
) are directly depending on Wasmtime.Therefore a downgrade from version
2.0.0
to version1.0.0
was necessary to fix this issue forwasmi
.In the long run we (
wasmi
team) might have to ship our own WASI implementation or find an alternative solution since we do not want us to depend on Wasmtime or any other Wasm runtime.