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 support #78
Comments
Not sure. Haven't tested this with WASM before, so I'm guessing some weird interaction is going on... |
I'll say! Would you like me to provide you with an MRE? Or, even better than an MRE, maybe contributing a check for that in your GitHub actions? I can open a PR. |
I'm unlikely to get around to fixing this any time in the next few weeks, given other personal stuff. If OTOH, you've got a PR that both demos the error and fixes things, I'd be interested and able to review that a lot sooner. |
I'm not sure I could fix it, but I could certainly provide a test. And no need to prioritize this over personal stuff. |
Having just read Although so does For reference, once I fix that (PR to come once I'm able to reproduce this in something that isn't
|
#82 should fix this. @cryptoquick Can you test that branch against your use case please? |
I've merged #82 and so closing this. Please re-open if there's still an issue with your use case. |
Was trying to do something like this:
But received this compile-time error:
It's strange, since async should be enabled by default according to the docs. Am I missing something, or is using this in a WASM context not yet possible?
The text was updated successfully, but these errors were encountered: