The interesting code for this example is:
c := a + b
There's no indication from that line of code what a and b are, a type system that doesn't do implicit conversions will tell you "error: adding string and int" and so the programmer can address the problem (e.g. maybe they meant to parse an integer from the string `a`, maybe they meant to format the integer `b` into a string).Using literals is not a useful comparison because there is no confusion about types in that case.
Having separate concatenation operator with implicit conversion could reduce that overhead:
Instead of: But this is not how Golang guys make decisions. And I'm fine with that nowadays as long as they don't claim to be right in that regard.