"The earlier implementation could not be driven to zero of them, because boxing was load-bearing in its emitter"
In the docs of the repo of their TS to C++ compiler.
<a href="https://github.com/geastack/compiler" rel="nofollow">https://github.com/geastack/compiler
I see what you’re getting at, but let’s not pretend like “load-bearing” is something that AIs made up. It was a turn of phrase long before AIs became mainstream and people are still allowed to use it.
"geatsc: the GeaStack TypeScript-to-C++ compiler. A clean-room rewrite built on one rule — a statically typed value that reaches a dynamic carrier is a defect, not a fallback."
The whole thing is like this
But to be fair, it's late 2026 so it's to be expected now that the vast majority of code and surrounding artifacts are AI generated. It's just a fact of life.
Heh, we spent 6 months writing and rewriting the compiler a couple of times and were just too excited about the final architecture. Thank you, simplified.
tarcon · · focus · HN ↗
In the docs of the repo of their TS to C++ compiler. <a href="https://github.com/geastack/compiler" rel="nofollow">https://github.com/geastack/compiler
odicjejcjej · · focus · HN ↗
not_a_bot_4sho · · focus · HN ↗
The whole thing is like this
But to be fair, it's late 2026 so it's to be expected now that the vast majority of code and surrounding artifacts are AI generated. It's just a fact of life.
dashersw · · focus · HN ↗
ptx · · focus · HN ↗