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
It's good that the current implementation can handle arbitrarily complex async functions, even with await statements inserted in arithmetic expressions run in a loop, but in most practical cases async functions can be easily transpiled into a chain of .then(...) calls. I'm wondering why this approach wasn't taken: transpiling to .then(...) if possible and transpiling to yield if not.
If would be nice to switch to async/await in my project, which is full of .then(...) chains, but it's not possible because even simplest async functions would turn into huge state machines that are neither readable nor debuggable.
The text was updated successfully, but these errors were encountered:
It's good that the current implementation can handle arbitrarily complex async functions, even with
await
statements inserted in arithmetic expressions run in a loop, but in most practical cases async functions can be easily transpiled into a chain of .then(...) calls. I'm wondering why this approach wasn't taken: transpiling to .then(...) if possible and transpiling toyield
if not.If would be nice to switch to async/await in my project, which is full of .then(...) chains, but it's not possible because even simplest async functions would turn into huge state machines that are neither readable nor debuggable.
The text was updated successfully, but these errors were encountered: