You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rust-lang/rust@aff7bd66e8b moves the two apis into one, and then a later commit makes them take a Vec directly since that is the destination for Rust's one internal consumer (test). Seems like either we need to RFC a supported api into Rust to make wasm-glue possible, or the wasm target compiler should already redirect stdout and stderr to the javascript console.log and/or both.
The text was updated successfully, but these errors were encountered:
Hey @markwal I'm just writing the second wasm framework and I found out the support for println is even worse... So I've written a comment in the closed Rust issue - rust-lang/rust#31343 (comment) and I hope there will be a solution. I would like to use wasm-glue in both frameworks (Seed, MoonZoon).
rust-lang/rust@aff7bd66e8b moves the two apis into one, and then a later commit makes them take a Vec directly since that is the destination for Rust's one internal consumer (test). Seems like either we need to RFC a supported api into Rust to make wasm-glue possible, or the wasm target compiler should already redirect stdout and stderr to the javascript console.log and/or both.
The text was updated successfully, but these errors were encountered: