-
Notifications
You must be signed in to change notification settings - Fork 62
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
From wasm32-unknown-unknown
to wasm32-wasi
#204
Comments
|
temeddix
changed the title
From Jan 29, 2024
wasm32-unknown-unknown
target is too limitedwasm32-unknown-unknown
to wasm32-wasi
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Report
Rinf does smoothly connect Flutter and Rust right now, but there's one clunky part left: the web.
On the web, with the curren target
wasm32-unknown-unknown
, many native functionalities includingstd::thread
,std::time::Instant
,std::fs
are not working. This limitation prevents many crates liketokio
andrayon
from working on the web, leaving the vast majority of Rust ecosystem being fallen out from the web platform.The goal is to use
wasm32-wasi
target for the web, so that users can use Rusts's thread, time, file, network APIs and various crates just like they do on native platforms. If we are able to compile Rust crates towasm32-wasi
, the JavaScript polyfill libraries will handle the rest, utilizing existing web APIs.This is a tracking issue, as this goal cannot be achieved without community support.
wasm32-wasi
targetwasm32-wasi
targetwasm32-wasi
targetSteps to Reproduce
Use any kind of system I/O functionalities on the web. It's very clunky, sometimes even panicking.
System Information
Not really relevant.
The text was updated successfully, but these errors were encountered: