-
Notifications
You must be signed in to change notification settings - Fork 80
Allow async function to be imported/exported #39
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
Comments
It is up to the implementation to ensure it provides a sync API. In Node.js it is always possible to syncify any call though on the implementaiton side by creating a worker thread and using atomics to synchronously wait on a shared lock in the worker that is performing asynchronous work. Usually it's best to just have a fully sync implementation though. |
Have you guys seen the work Joel Dice did here: https://github.com/dicej/isyswasfa/tree/main It's very experimental at this point and only in Rust, but looks like it will be very useful when he gets to JavaScript. |
Yes, we will follow in this path in the Jco project, where functions may support both sync and async variants depending on the canon ABI option passed. Preview 3 support is a little way off though still. If anyone is interested in prototyping in the mean time along a similar lines, work here would be welcome. |
linking here for reference: dicej/isyswasfa#1 (comment) |
Hey @eduardomourar with the merge of experimental JSPI integration this should be possible in As extra context, see #551 which contains some pieces of an alternate approach (asyncify), and updates to the browser bindings. We hope to get the experimental browser-side bindings updated but there's not a great timeline just yet on when that PR will be reformulated/can be finished (if it will even make sense, given growing support for JSPI). I'll close this issue for now -- please feel free to comment if you think it should be re-opened. |
There are certain cases where the host/guest implementation needs to pass an asynchronous function. Can this be supported in the JavaScript codegen even when the WIT definition has its signature as synchronous?
The text was updated successfully, but these errors were encountered: