-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Implement bytes_stream() for wasm. #1713
Implement bytes_stream() for wasm. #1713
Conversation
I think a question I always had with this PR was what are the consequences of pulling in that crate. Sometimes wasm things surprise me. Are there any concerns that we should know about? Like does it require more specific wasm targets? Or if we change the dependency later, would that cause people issues? |
I'm not aware of any concerns pulling in the wasm-streams crate. It solely supports |
The
Me too... 😅
I think it should be fine. It supports |
Alrighty, thanks for clarifying! We can merge, though looks like CI is grumpy. |
Co-authored-by: muji <muji@tmpfs.org>
01bc4b2
to
a4a549e
Compare
Indeed. There was also an issue with imports that should only be imported if the Edit: tested this branch with our Yew app and that seems to work! |
Co-authored-by: muji <muji@tmpfs.org>
Adds support of
Response.bytes_stream()
to the wasm32 target.Follow up of: #1576
Fixes #1704
Todo: