Skip to content
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

Support Asyncify for Blazor scenarios #48713

Closed
AaronRobinsonMSFT opened this issue Feb 24, 2021 · 3 comments
Closed

Support Asyncify for Blazor scenarios #48713

AaronRobinsonMSFT opened this issue Feb 24, 2021 · 3 comments
Labels
arch-wasm WebAssembly architecture area-Codegen-LLVM-mono
Milestone

Comments

@AaronRobinsonMSFT
Copy link
Member

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

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Feb 24, 2021
@AaronRobinsonMSFT AaronRobinsonMSFT added the arch-wasm WebAssembly architecture label Feb 24, 2021
@ghost
Copy link

ghost commented Feb 24, 2021

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

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

Author: AaronRobinsonMSFT
Assignees: -
Labels:

arch-wasm, area-Codegen-LLVM-mono, untriaged

Milestone: -

@lewing lewing removed the untriaged New issue has not been triaged by the area owner label Feb 24, 2021
@lewing lewing added this to the Future milestone Feb 24, 2021
@lewing
Copy link
Member

lewing commented Feb 24, 2021

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.

@lewing
Copy link
Member

lewing commented Jun 18, 2021

The limitations around this approach in the browser scenario make it unsuitable for a general sync over Promise solution.

@lewing lewing closed this as completed Jun 18, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Jul 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-Codegen-LLVM-mono
Projects
None yet
Development

No branches or pull requests

2 participants