feat: Add WASI Preview 2 support and enhanced target coverage #3507
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
avrabe
force-pushed
the
wasi-p2-support-pr
branch
5 times, most recently
from
0152ded to
d68b726
Compare
- Add WASI version constraint settings and platform configurations for wasip2 - Add support for wasm32-wasip2 and wasm32-wasip1-threads targets - Fix WASI toolchain and allocator library issues for cross-compilation - Add comprehensive unit tests and documentation for WASI platform functionality
avrabe
force-pushed
the
wasi-p2-support-pr
branch
from
d68b726 to
7249b22
Compare
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.
Summary
This PR implements comprehensive WASI Preview 2 support for rules_rust, addressing the feature request in #3502.
Changes
wasm32-wasip2andwasm32-wasip1-threadstargetsCloses #3502
Additional Notes
This implementation provides forward compatibility with the evolving WASI ecosystem while maintaining backward compatibility with existing wasip1 targets.