Hacker News Reader

I think you might be waiting for awhile unfortunately. Implementing await would result in a lot of autogenerated code. Typescript is largely meant to be almost 1:1 with the Javascript it produces.

Anders talks about that problem in this video: http://channel9.msdn.com/Events/Build/2013/9-006

Awaiting for awhile? Awful.

There's also a discussion[1] at Codeplex on some TypeScript compatible alternatives to async/await.

[1] http://typescript.codeplex.com/discussions/397594

One proposed alternative to await (for CoffeeScript) that is more one-to-one with the generated JavaScript: https://github.com/jashkenas/coffee-script/issues/2762

That would result in future incompatibility, considering ES6 has generators which could do the same job.

edit: just the points

We will care about this in 2050 - when ES6 gets released.

FWIW await is in the Roadmap for 1.x http://typescript.codeplex.com/wikipage?title=Roadmap