We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Asyncify permits making an existing synchronous API utilize a JavaScript/WASM asynchronous based API.
An example of the Julia runtime adding support - JuliaLang/julia#32532.
See #37669
/cc @steveisok @lewing @marek-safar
The text was updated successfully, but these errors were encountered:
Tagging subscribers to 'arch-wasm': @lewing See info in area-owners.md if you want to be subscribed.
arch-wasm, area-Codegen-LLVM-mono, untriaged
arch-wasm
area-Codegen-LLVM-mono
untriaged
Sorry, something went wrong.
For background https://kripken.github.io/blog/wasm/2019/07/16/asyncify.html covers the benefits and limitations. The limitations there are hard to avoid in the current runtime but we should expand on the reasoning here.
The limitations around this approach in the browser scenario make it unsuitable for a general sync over Promise solution.
No branches or pull requests
Asyncify permits making an existing synchronous API utilize a JavaScript/WASM asynchronous based API.
An example of the Julia runtime adding support - JuliaLang/julia#32532.
See #37669
/cc @steveisok @lewing @marek-safar
The text was updated successfully, but these errors were encountered: