Port create-exe and the wasmer C API over to the webc compatibility layer #3944
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
Michael-F-Bryan
changed the title
syrusakbary
approved these changes
Jun 2, 2023
ptitSeb
approved these changes
Jun 2, 2023
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.
To future-proof the Wasmer project against new versions of webc being released, we need to make sure any code accepting a webc file as input goes through the
webc::compat::Containertype (our version-agnostic compatibility layer).This PR updates
wasmer create-exeand the C API to use the compatibility layer.The
wasmer-registrycrate was also quite tightly coupled to thewebc::v1module, but that code was only ever used by the oldwasmer runcommand (removed in #3924) so I've deleted it.