feat: add support for wasm targets #1711
Draft
+171
−82
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
HoKim98
force-pushed
the
feat/wasm
branch
3 times, most recently
from
62a1f28 to
875344b
Compare
Signed-off-by: Ho Kim <[email protected]>
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.
Which issue does this PR close?
What changes are included in this PR?
Add support for WASM targets below:
Are these changes tested?
Currently there build steps below are passed on my local machine:
cargo build --package parquet --target wasm32-wasip1 -p parquet --no-default-features --features tokiocargo build --package parquet --target wasm32-wasip2 -p parquet --no-default-features --features tokioThese steps are still in progress:
parquet's WASM support (single-thread support):AsyncFileWriterdoesn't need to beSendarrow-rs#7612OpenDAL's WASM support for storage backends