I think the point is, if you write map like this you might as well be using a dynamically typed language in the first place because you're deriving no benefit from the type checker. In fact, you're just using casting to completely circumvent it.
Of course. If the main cornerstone of your project is map it's probably not the greatest idea to use Go, but if you're using Go for other reasons and happen to need a quick map function there's no reason to change languages just because Go doesn't have a standard library implementation
But then it's pretty odd to use Go because you like the language, while not being able to design a proper map().
And map() btw is only the tip of the iceberg in functional programming. But then again, Go is not a functional programming language.
Re:Golang Diaries II
by burntsushi on Monday July 15, 2013 @10:16PM
(#6049686)
Here is something that is less onerous on the caller, but probably slower. [1] Here's the source. [2]
[1] - https://github.com/BurntSushi/ty#examples [2] - https://github.com/BurntSushi/ty/blob/master/fun/list.go#L17
http://play.golang.org/p/jxMFq5UYs1