You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Posting this so that I don't forget that I want it.
Once library files can use beyond ES5 (probably through Babel, #6000), it would be great if async functions could be actual async JS functions, as it's simpler and would greatly reduce the boilerplate code.
What I'm imagining is that instead of the Emterpreter FFI system pausing when EmterpreterAsync.handle is called, it would check if an FFI returns a promise, and if so pause and await it. Easy to describe in simplistic terms, I'm sure it will take a lot of work :P
The text was updated successfully, but these errors were encountered:
curiousdannii
changed the title
EMTERPRETER_ASYNC: use async JS functions
EMTERPRETIFY_ASYNC: use async JS functions
Jan 15, 2018
This issue has been automatically marked as stale because there has been no activity in the past year. It will be closed automatically if no further activity occurs in the next 7 days. Feel free to re-open at any time if this issue is still relevant.
Posting this so that I don't forget that I want it.
Once library files can use beyond ES5 (probably through Babel, #6000), it would be great if async functions could be actual async JS functions, as it's simpler and would greatly reduce the boilerplate code.
What I'm imagining is that instead of the Emterpreter FFI system pausing when EmterpreterAsync.handle is called, it would check if an FFI returns a promise, and if so pause and await it. Easy to describe in simplistic terms, I'm sure it will take a lot of work :P
The text was updated successfully, but these errors were encountered: