8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Now that async/await support has reached stage 3 in the TC39 proposal process, time to remove the --experimentalAsyncFunctions flag
--experimentalAsyncFunctions
Sorry, something went wrong.
Remove --experimentalAsyncFunctions
92f1b48
Remove --experimentalAsyncFunctions from tests
e9bed76
lgtm.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
do we now have ES5 support for async functions? What happens if you target ES5 and then use an async function?
there should be another message Async functions are only available when targeting ECMAScript 6 and higher. which i have not changed
Async functions are only available when targeting ECMAScript 6 and higher.
👍
I had to lookup and see what TC39 was. It is a well documented here: http://tc39.github.io/ecmascript-asyncawait/
Merge pull request #5231 from Microsoft/removeExperimentalAsyncFunctions
99d448a
Remove experimental async functions
https://github.com/Microsoft/TypeScript/wiki/Compiler-Options needs an update... this flag is still mentioned there without deprecation note.
Is there a way to use async/await but still target ES5? I mean, there is many envs which do not support ES2015 100%, but they support yield. So would be good to target ES5, but still use yield and async/await.
yield
For the time being, no. But we're working on supporting async/await in pre-ES6 targets.
@DanielRosenwasser thanks. Just got the idea: TS -> ES6 and then transpiling to ES5 via Babel with disabled yield transpilation.
TS -> ES6
Successfully merging this pull request may close these issues.