Repository navigation
Replies: 1 comment
|
I would love to, it be fun, and it could actually speed up the compiler, since the current C++ code does a lot of object allocation that I've already spent time optimizing. The reason that hasn't happened yet has mostly to do with pragmatism: I wanted Goose to be runnable on new platforms and in new situations as easily as possible. Writing it in Goose means we must ship a C output blob for easy compilation. That must be kept up to date. Any bugs people find will now first appear in this C output, and need to be correlated back to the original Goose code, which is not always easy.. this will either need a good Goose native debugger, or plenty of LLM analysis. So in summary, it complicates the practical use and development of it a bit, just for the sake of language purity. That was initially not a good tradeoff. I am sure we'll do it eventually, but I am not in a hurry, while so much of the language and ecosystem are still being figured out. |
Uh oh!
There was an error while loading. Please reload this page.
I mean eventually having the Goose compiler written entirely in Goose itself, so that Goose can compile its own compiler?
Does Goose currently have all the necessary language features to implement its own compiler?
All reactions