Allow to compile to wasi target without wasm_bindgen #746
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
|
Sweet, thanks! CI passed for stable rust so I'm merging 👍 |
llebout
pushed a commit
to llebout/yew
that referenced
this pull request
Jan 20, 2020
* allow to compile to wasi without wasm-bindgen * allow to compile to wasm32-wasi without wasm_bindgen
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.
I am trying to compile yew worker to wasm32-wasi, though now it also includes wasm_bindgen which is not compatible with wasi environment. Wasi allows to execute POSIX-like compatible services e.g. databases, math, lambdas... IMHO it is quite important that yew supports compilation of its workers to WASI as a transitive dependency.
These are few examples where yew is compiled to WASI target:
https://crates.io/crates/wasi-worker-yew
https://github.com/dunnock/wabench/
http://wabench.com:8080/