5 ms·
Am justing waiting for them to implement "await".
by deadreturns3 13y ago
Am justing waiting for them to implement "await".
- Permit 13y agoI 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 http://channel9.msdn.com/Events/Build/2013/9-006
- CmonDev 13y agoAwaiting for awhile? Awful.
- yareally 13y agoThere's also a discussion[1] at Codeplex on some TypeScript compatible alternatives to async/await. [1] http://typescript.codeplex.com/discussions/397594 http://typescript.codeplex.com/discussions/397594
- omphalos 13y agoOne proposed alternative to await (for CoffeeScript) that is more one-to-one with the generated JavaScript: https://github.com/jashkenas/coffee-script/issues/2762 https://github.com/jashkenas/coffee-script/issues/2762
- jeswin 13y agoThat would result in future incompatibility, considering ES6 has generators which could do the same job. edit: just the points
- deadreturns3 13y agoFuture incompatibility and TypeScript. You're funny.
- CmonDev 13y agoWe will care about this in 2050 - when ES6 gets released.
- itsmonktastic 13y agoFWIW await is in the Roadmap for 1.x http://typescript.codeplex.com/wikipage?title=Roadmap http://typescript.codeplex.com/wikipage?title=Roadmap