X (formerly Twitter) ·
A few days ago, I started rewriting the typescript compiler after I got tired of it consuming gigabytes of memory when type checking the Cloudflare dashboard Just got to 50% of the typescript compiler and conformance suite They run in 400 ms and with peak memory of 79 MB
Somewhat proud of the architecture. It’s still CLI of course with an identical interface to typescript go I use a shared memory arena with interior mutability for types Completely thread safe and multithreaded
I’m very actively ensuring no clones or allocations unless necessary so every single type representation is stored at most once
Just got type declaration support for the typical libs done and directive support for tests That was painful Every couple of sessions, I hit an infinite loop because I forget a recursion guard or a visited set or memo
The conformance and compiler tests are fantastic though, very helpful and thorough as hell (as you would expect) There’s about 15,000 of them and we now pass half
I’ll publish and open source once I get to full conformance and perhaps after another memory audit
I even do strutural sharing so type storage in memory is efficient across multiple tests in a suite that all import type declaration libs that have overlap
Does the "gigabytes of memory" apply to the Go-based TS 7.0 preview?