Also, having a map implemented in a library is a Good Thing. It means that your language is extensible and expressive enough for this. AFAIK Go is - by design - not that extensible.
Auto-conversion: "2" + 5 = "25". This looks horribly hackish, like some type buggering perl might do, or js. But it comes in handy when you want to build a message string.
And yes, as the article tells us, a lot of things are very purposely left out of Go, which has advantages and disadvantages like most trade-offs.
string hello = "hello";
string world = "world";
string hw = hello + ' ' + world;
Auto-conversion: stringstream ss;
ss << "2 + 2 = " << 2 + 2 << endl;
string result = ss.str();"nice try" on "auto-conversion".
And this is a problem because?
(It's actually a weak point of Go that you cannot define them in a library without sacrificing type safety.)
C++11 has a GC API defined.
Reference counting is part of any GC book in CS speak.
However, I feel that doing the "implicit casting" thing only for the single, limited case of string concatenation strikes a happy medium between providing useful convenience and giving you enough rope to hang yourself with.