3 ms·

Any plans for a AOT version of Typescript with strict typing that targets WASM or LLVM?

• Ciantic 2y ago
  This is what I would have liked too: Figure out a sufficient subset of TypeScript that can be compiled to native/WASM and then write TSC in that subset. While I like faster TSC, I don't like that the TypeScript compiler needs to be written in another language to achieve speed; it kind of reminds everyone that TS isn't a good language for complicated CPU/IO tasks. Given that the TypeScript team has resigned to the fact that JavaScript engines can't run the TypeScript compiler (TSC) sufficiently fast for foreseeable future and are rewriting it entirely in Go, then it is unlikely they will seek to do AOT.
  • pjmlp 2y ago
    This already exists, Static TypeScript https://makecode.com/language https://makecode.com/language https://www.microsoft.com/en-us/research/publication/static-typescript/ https://www.microsoft.com/en-us/research/publication/static-...
    • DanielHB 2y ago
      If it is not supported by the same team that supports typescript it is not really usable in real world applications.
      • pjmlp 2y ago
        I guess the same applies for using Go then.
• spankalee 2y ago
  If you squint, Porffor[1] might end up being something like that. It doesn't use type hints yet, and the difficulty there is that you'd need a sound type system in order to rely on the types. You may be able to use type hints to generate optimized and fallback functions, with type guards, but that doesn't exist yet and it sounds like the TypeScript team wants to move pretty quickly with this. [1]: https://porffor.dev/ https://porffor.dev/