Skip to content
New issue

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

Crazy idea to make an always up to date language-typescript equivalent #1

Open
CRogers opened this issue Jul 25, 2015 · 1 comment
Open

Comments

@CRogers
Copy link
Contributor

CRogers commented Jul 25, 2015

Brain dump of an idea I just had before I go to sleep to get around the language-typescript problem:

  1. Make a .d.ts of https://github.com/Microsoft/TypeScript/blob/master/src/compiler/types.ts *.
  2. Somehow convert this to haskell ghcjs ffi, either by using this tool or manually.
  3. Rebuild this tool using the actual typescript parser and types (run it using ghcjs).
  4. We can then automatically regenerate step 2) using this tool rather than doing it manually.
  5. ???
  6. Profit

The parser should always be up to date and accurate this way. Requires integrating with typescript though.

* Well, the subset needed by the parser.

@mgsloan
Copy link
Contributor

mgsloan commented Jul 29, 2015

That's an awesome idea, I like it!

As mentioned in your PR, it seems that language-typescript is either a bit out of date or lacking some features for parsing these definition files. Here's the modifications I needed to make to the ace.d.ts to get it to build: 91173fd

So, probably to bootstrap this for step 2, we can just manually cut down the typescript compiler's definitions till they work with the current tool (possibly filling in some of the missing cases in the code).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants