Earlier quoted context omitted.
It's real shame it's kinda bad language for it. Looking at what people did with Rust macros it's shame that Go code generation story is either "just run some random binaries to compile stuff" or "put code instructing the compiler to do stuf in fucking comments " And I say it without being sarcastic but Go makes me miss C preprocessor and nothing should make anyone miss C preprocessor.
>Looking at what people did with Rust macros it's shame that Go code generation story is either "just run some random binaries to compile stuff" or "put code instructing the compiler to do stuf in fucking comments" Why is it a shame? Rely on macros and this is what you get: 1. Slow compile times 2. Unsearchable (grep, sourcegraph...) code 3. Magic codebases. Longer learning curve To me, working in a large organizatio…
Re: Building a High Performance Data Integration Framework in Go
#31The article is about code generation that is more magic than macros.