Migrate from cargo component to the new wasm32-wasip2 target. #19
Conversation
This file contains hidden or 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
Now that wasm32-wasip2 target has [reached Tier 2 support in Rust], this is a patch switching the hello-wasi-http demo from using cargo-component to using the new wasm32-wasip2 target. [reached Tier 2 support in Rust]: https://blog.rust-lang.org/2024/11/26/wasip2-tier-2.html
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Now that wasm32-wasip2 target has reached Tier 2 support in Rust, this is a patch switching the hello-wasi-http demo from using cargo-component to using the new wasm32-wasip2 target.
This removes a lot of boilerplate, which is nice. However, cargo-component has some support for managing dependencies, which is useful if users want to add non-WASI WIT files, which the core cargo tooling doesn't. So I'm just posting this as a draft for now.