Neither Go nor C has static assertions, the macro in questions uses clever techniques to implement one in C, but you probably can't do that in Go. So C is more powerful here.
Another example of clever C macro use is implementation of foreach loop (C doesn't have foreach) in linux kernel, here's question about it:
http://stackoverflow.com/questions/15754236/how-do-i-use-the...
> Neither Go nor C has static assertions
C11 has: _Static_assert(const_expr, fail_string)I haven't really used C after I graduated and I remember my professor showing us how to implement static assertion :)
[ Disclaimer: I'm a maintainer of runC and have been programming in Go for many years. But that doesn't mean I have to like the language. Give me C any day. ]
Personally I think Go actually makes a pretty bold statement about dependency management: people don't know what they want. I also have a sneaking suspicion Git and Github's interface in no small part to blame.
Golang for me made me come to one important realization: if I can't build a project by just cloning the git repository, then why the hell not?
If you have not experienced this before, try cloning a repo that uses Go-1.6-style vendoring anywhere outside the GOPATH.