-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update wasmtime #35
update wasmtime #35
Conversation
Update to latest stable release of Rust, this is required to build wasmtime's latest release. Signed-off-by: Flavio Castelli <fcastelli@suse.com>
The lint `const_err` has been removed: converted into hard error, see issue #71800 <rust-lang/rust#71800> for more information Signed-off-by: Flavio Castelli <fcastelli@suse.com>
Update wasmtime-provider to consume latest version of wasmtime Signed-off-by: Flavio Castelli <fcastelli@suse.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -44,7 +44,6 @@ | |||
clippy::equatable_if_let, | |||
bad_style, | |||
clashing_extern_declarations, | |||
const_err, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@flavio @jsoverson Does removing this require the wapc-codec
, wapc-guest
, wapc-pool
, wasm3-provider
, and wapc
crates to be version bumped in addition to the wasmtime-provider
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, this is not required. Clippy focuses only on the warnings produced by the user code, not by its dependencies
This time the update to latest version of wasmtime required some small changes:
Once this is merged, a new version of the wasmtime provider must be tagged and released.
Note: I did not bump the version of the wasmtime-provider. I can do that if you want, it would just be a patch bump