Erik Demaine

FWIW, looking at the code, this would actually be done in the lexer, in the `identifierToken` method (which already deals with lots of pseudo-keywords). It already deals with `IDENTIFIER:` all...

@GeoffreyBooth I generally agree, except for `:=`. That symbol means assignment in so many languages (Python in particular) that I don't see it as type annotation... That said, I don't...

This is getting a little off topic for this thread, but given the mention of a compiler flag for TypeScript: this might be worth reconsidering. I've been noticing at the...

Cool, I didn't know about `Object.defineProperties`; that's definitely nicer, and should at least make it possible for TypeScript to understand it's type (whereas multiple calls to `Object.defineProperty` wouldn't be consistent...

You can actually switch the TypeScript playground to JavaScript input mode under the "TS Config" menu. If you also turn on `strictNullChecks` (which I believe is common), you also get...

I think #5395 could help with the original issue here. Currently, that PR doesn't push the `var` declaration down to first assignment if there's an attached comment (so that the...

I assume @JanMP's goal would be able to write `.coffee` (or `.tcoffee` or whatever) files and have Meteor automatically translate them via CoffeeScript + TypeScript, in particular for type checking....

I [started a branch](https://github.com/edemaine/coffeescript/tree/typescript) that adds basic type annotation support. For example: ```coffee i ~ number i = 5 i = 'hello' j ~ number = 10 zero ~ ->...

@GeoffreyBooth Thanks for the quick positive feedback! Here are some responses / further comments: * In testing, I found one reason we might want a `.tcoffee` or `.tcs` extension: `tsc`...

Hmm, interesting idea. I'm not very familiar with JSDoc so don't know how much feature parity it has to TypeScript. But given the extensive work to support JSDoc already in...