It is just extremely frustrating to see them using contradictory arguments for various parts of the language. This is a very liberal way to do this, which contradicts most of the rest of the language (library dependencies, language itself, features).
For instance in this case, the very existence of the code generation libraries contradicts the reflection package.
Compile-time function execution would have been so much more consistent it's horrifying :
http://dlang.org/mixin.html
Example vaguely similar to Go's example:
http://forum.dlang.org/thread/lgunf8$14rp$1@digitalmars.com#...
http://stackoverflow.com/questions/18552454/using-ctfe-to-ge...
But like every other decision in Go, you can either assume the Go developers actually believe the arguments they're putting up ... or you can ask yourself "would the Go compiler/toolchain become easier or harder to implement ?" And use that argument as almost the sole argument for any decision. One of these ways of thinking explains every decision very consistently, the other leaves one listing the exceptions.
And the right solution, mixins + CTFE is legendary hard to implement. As in, someone who's written 3 commercial C++ compilers from scratch has serious trouble getting it to work.
But it's such a joy to use.