-
-
Notifications
You must be signed in to change notification settings - Fork 195
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
[ES7] Basic support for async functions/methods #140
Comments
As mentioned by @nzakas in #125 (comment)
|
@nzakas does not seem opposed to implementing this future, as mentioned in eslint/eslint#1657 (comment):
I personally don't know how to implement it and I understand it can be much work, that's why I thought it would be worth proposing a intermediary solution. |
I can speak for myself here: we aren't implementing experimental features. If you need such support in ESLint, you can use babel-eslint. |
This is no longer experimental, is in stage 2, and implemented in Edge. I'm thinking it might be time to support async. |
Stage 3 even? tc39/ecma262@2fa3ca4 |
Though i assume this will get swallowed up by #200 |
Want this too. 😢 Currently I use |
+1, would love to avoid |
@benjamine This issue is a bit out-of-date; if you're using ESLint 3.6.0 or higher, you can now use |
I use them in many projects notably for class methods because the syntax prevents me from easily using workarounds such as
Bluebird.coroutine(function * generator() {})
.Unfortunately doing so breaks parsing and prevents EsLint from finding other errors.
I understand that fully implementing async functions could be a lot of work and that it is not a priority to support ES7 features for now but a preliminary support such as simply removing them from the source would at least allows the parsing of the rest of the code.
The text was updated successfully, but these errors were encountered: