-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Experimental support for ES7 async/await #8
Comments
I'd love this too. I remember @benjamn built a recast transform for async await. Everyone I know who uses jstransform (ourself included) would love to switch to recast ASAP, so when we do it's nice to know there's a transform waiting. Typing async/await wasn't too hard to do for Hack, so it shouldn't be too hard to do in Flow too, once there is demand for it! |
async/await is supported in regenerator proper right now; I think that es7-async-await package is old. |
That's right, I've stopped working on https://github.com/benjamn/es7-async-await in favor of handling |
I should also mention that 6to5 uses Regenerator for its |
+1 |
It would be particularly awesome if Flow could somehow warn when exceptions might be swallowed by |
Yes async await would be a very nice addition! Any updates on progress? :) 👍 |
+1 demand :) |
+1 love this too. |
+1 I get Is there anyway to workaround this? |
👍 |
Async/await support added in v0.12. |
Ensure lexer expects XJS child after nested close
I'm still getting errors for the |
@johngeorgewright can you give an example? |
/* @flow */
function somethingParallel() {}
function somethingElseParallel() {}
async function somethingAsynchronous() {
await* [
somethingParallel(),
somethingElseParallel()
];
}
|
|
@johngeorgewright Thanks. The closest thing I could find as far as documentation is this section of the proposal, but I'm not sure if that is being tracked along side async/await in the ES process. I will note that Babel seems to understand this syntax, so it could very well be an omission here. @sebmck, sorry to drag you into this, but do you know what's up with this feature? Is it a part of the "standard" async/await feature, or is it on a separate schedule/phase? |
No worries at all. |
Ah, OK, sorry. So I'm to use |
I have fallen in love with 6to5 and traceur's support for async/await. I would love to be able to use this with flow.
The text was updated successfully, but these errors were encountered: