New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document the WebAssembly story #14
Comments
I created a basic example of stdweb + wasm32: https://github.com/lilianmoraru/stdweb-alert-example I did something wrong or the support is not great(stdweb or/and Rust + emscripten) but while trying to make |
@lilianmoraru Yes, the way you're using it isn't really supported (yet). Basically, Rust's Emscripten-based wasm target requires a hefty runtime which you can find in the Rust is going to have a native wasm target where it'll only generate a standalone |
Is it even possible to support the new target without some help of the compiler, as I don‘t see how you could do the JavaScript literals without the emscripten API or the compiler support for it |
Currently it might not be, but I see no reason why we wouldn't be able to work something out. (I'll add it myself if I have to.) |
I believe that wasm32-unknown-unknown is now available from rustup on nightly. |
@emosenkis stweb wasm32-unknown-unknown does not currently work with it because it requires an event loop that is available only inside the emscripten environment. |
Since WebAssembly is now supported on every target that Rust supports - closing! |
As far as I can tell this library currently does not support wasm. But since Rust now supports wasm on stable it would be useful if documentation existed somewhere detailing this libraries future plans for supporting wasm,
or if it already does and I missed that, there should be docs on how to use this library with wasm.Edit: After fiddling a bit, I have determined that at the very least the todomvc example can run under wasm. This just means that it is unclear if wasm is actually supported or if this is something that is not guarenteed to work going forward.
The text was updated successfully, but these errors were encountered: