First of all, you're making the enterprise java argument. Which is valid, but drives me to suicide.
Furthermore ... Go ... succinct ... elegant ... using reflection as an alternative to generics ...
In my experience Go is neither succing (if err { ... } one-statement if err { ... } one-statement if err { ... } one-statement). It is extremely inelegant because due to the confused sequence of statements it isn't possible to keep your thoughts on what the method is doing, as there are constant error handling concerns everywhere (or regrets/TODOs about error handling to be completed in the future ...)
Is this
(if this doesn't refer to itself or the sentence it's in, return that information to the caller manually so he can ignore it)
somewhat
(if the above statement is not and adjective you have a problem with your understanding of english, report to the relevant authorities)
unclear
(if un doesn't result in the reversal of the meaning of the word clear, we have a problem and should inform the main sentence interpretation routine that understanding is flawed)
perhaps
(missing error checking)
?
(if the above is not punctuation, report back that your browser is probably not using the correct character set)
Using reflection as an alternative to generics is horrible in lots of ways, but just mentioning a few : no type safety (not even a decent verification you're passing the correct number of arguments). It's extremely long code, full of edge cases (such as arrays being a value type and slices being a reference pointer despite differing only in a single character). And it's sloooooooooooooow. As in ruby slow.
And you forgot Go crashes. If you think C++ error messages are long, you haven't seen a nil-pointer dereference in Go.