Conversation
- fixed label fall-through - added implicit return - disallow 'with' in async - fixed ASI ambiguity with 'async' by disallowing newline - cleanup rewrite of ForInStatement
…t in some rewritten nodes
…nged how catch variables are renamed
…ating unique generated identifiers
…ve comments in rewrite
src/compiler/checker.ts
Outdated
There was a problem hiding this comment.
When you say "the type has a construct signature...", you don't really mean the type. You mean the type resulting from resolving the name of that type as a value.
src/compiler/parser.ts
Outdated
There was a problem hiding this comment.
I understand now. This is very ES6-y. I prefer the model where ambient flags are passed by just doing nothing, and flags are explicitly turned on and off. I know that what you've done here is more to the grammar, but for some reason I find it less intuitive.
|
Hello @rbuckton, I've tried to use your branch and found a compiler crash. Using this code: gives this output: I am using node 0.12.2 x64 on Windows 8.1 and the tsconfig.json is: Hope this helps! |
|
closing this in favor of: #3078 |
|
@mhegazy does this mean async functions are only supported in ES6? Then why is that? |
|
@tinganho Downlevel support for async functions will likely end up in a separate PR. This one is extremely out of date. |
|
Ok thanks for explanation @rbuckton . I really want this feature in at least ES5 too. |
|
@teobugslayer perhaps it's related to #3978, with the difference that one is in the |
|
Changes Unknown when pulling d57fe72 on prototypeAsync into * on master*. |
Support for Async Functions, as per the proposal in #1664.
__awaiterand__generatorhelper functions to emit output (emitter.ts)