Closures are the Generics for Go (medium.com)

It's interesting that they cite DRY as one of the reasons for refactoring the code to use closures, as it appears that in their later example of sorting, the two lambdas they pass for sorting ints and strings are identical other than type. Interestingly, it looks like that repetition could be solved by a macro that generates the function given a type. I'm not surprised super familiar with Go; I'm guessing that it doesn't have any sort of macro system that could do this, or else they would have mentioned it?

If I had to choose between no generics or "generics as closures" I'd vote no generics.