This repository has been archived by the owner on Oct 31, 2023. It is now read-only.
feat: Migrate to wasmer 3.3.0
#236
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
TomAFrench
changed the title
wasmer 3.3.0wasmer 3.3.0
phated
reviewed
Aug 14, 2023
phated
approved these changes
Aug 15, 2023
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Problem*
Prerequisite for noir-lang/noir#2235
Summary*
This PR migrates us to
wasmer3.3.0 as using noir-lang/acvm#494 while usingwasmer2.3.0 fails to compile.As part of this I've removed all of the code which handles the wasm32 target as this crate has never worked for that target and will be retired soon anyway.
Additional Context
PR Checklist*
cargo fmton default settings.BEGIN_COMMIT_OVERRIDE
feat: Migrate to
wasmer3.3.0 (#236)END_COMMIT_OVERRIDE