Update to Wasmtime 4.0.0 #217
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit upgrades to Wasmtime 4.0.0 which is the latest version of Wasmtime on crates.io. While Wasmtime 5.0.0 is going to be released tomorrow it's probably best to get this in first since there's a number of API changes here. The main change in Wasmtime 4 is some updates to `wiggle`-based APIs to handle shared memory. This means that previous accessors may sometimes have another failure condition. For viceroy though these failure conditions are always errors, so I've introduced a new `Error::SharedMemory` here to cover this case.
cratelyn
approved these changes
Jan 19, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit upgrades to Wasmtime 4.0.0 which is the latest version of Wasmtime on crates.io. While Wasmtime 5.0.0 is going to be released tomorrow it's probably best to get this in first since there's a number of API changes here.
The main change in Wasmtime 4 is some updates to
wiggle-based APIs to handle shared memory. This means that previous accessors may sometimes have another failure condition. For viceroy though these failure conditions are always errors, so I've introduced a newError::SharedMemoryhere to cover this case.