The article gives a good example what a mess C code can become if pointers are used. In C, the declaration for the example function looks like this, parameter names omitted. The function returns a function pointer and also expects a function pointer as the first parameter.
int (*(*fp)(int (*)(int, int), int))(int, int)
In Go, the same is much easier to read:
f func(func(int,int) int, int) func(int, int) int
That being said, Go also makes exceptions when needed. Read the article for more information.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There's a blog article about Go's declaration syntax that explains the reasoning behind it: blog.golang.org/gos-declaration-sy...
The article gives a good example what a mess C code can become if pointers are used. In C, the declaration for the example function looks like this, parameter names omitted. The function returns a function pointer and also expects a function pointer as the first parameter.
In Go, the same is much easier to read:
That being said, Go also makes exceptions when needed. Read the article for more information.