-
Notifications
You must be signed in to change notification settings - Fork 27
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
wasm-unknown-unknown support? #166
Comments
I see. From what I read, |
Could you try running your code with #167 ? I removed the use of reqwest's blocking feature, but there might be other issues that prevent building on wasm |
I've tried with
in dependencies, and when I run
I get the attached error log. |
Ugh ok, turns out hyper and tokio don't support wasm. The |
I've checked out the wasm branch locally. Running I've run |
Ah, I never tried compiling on windows. I think I remember that windows doesn't support symlinks; what do you see in |
Another potential issue is line endings: git tries to be clever with line endings on different platforms and that might break the abnf parser. But as far as I can see it works with dos line endings too. |
Aha. What was supposed to be the symlink was a text file containing the path to the target. Replaced it with the correct dhall.abnf, and it compiles. Also my project with a reference to the local serde_dhall also compiles now. |
I released version 0.5.3 that should support wasm and windows |
Thanks, that does indeed compile and work... until I actually try to use dhall's import mechanism. For example:
Then I get:
|
Ah >< I was afraid something like that might be the reason why reqwest didn't support blocking on wasm. Well then the only option is to make a big chunk of dhall-rust async. |
Thanks for your help on this anyway - it's now at a place where I've got something working. And my project is only a MVP / learn how a bunch of technologies work at the moment. |
I tried using serde_dhall in my seed project (compiling to wasm-unknown-unknown). This doesn't compile becuase it relies on the blocking feature of reqwest, which doesn't appear to be implemented in reqwest wasm mode.
The text was updated successfully, but these errors were encountered: