solod

> A transpiler should translate all of the language's semantics, including resolving identifiers as symbols, and then choose legal names for them in the target language. Yes, it should; but it also makes things much more difficult. This specific transpiler indeed builds an AST, but does not care about identifiers, just emitting them as is [1] (I hope I found the correct place in the code). [1]: https://github.com/solod-dev/solod/blob/8485bc867ae0f0269d75...

I'm curious if Solod https://github.com/solod-dev/solod would be a good fit. It's not "real" Go, but you write Go and generate C.

I was curious how defer is implemented. `defer` in Go is famously function-scoped, not lexically-scoped. This means that the number of actively-deferred statements is unbounded, which implies heap allocation. The answer is that Solod breaks with Go semantics here: it just makes defer block-scoped (and unavailable in for/if blocks, which I don't quite get). https://github.com/solod-dev/solod/blob/main/doc/spec.md#def...

Go is epitome of simplicity. Why on earth would you want to put another abstraction on top of it? There is Solod project that is Go subset that compiles into C that is more interesting https://github.com/solod-dev/solod