cpalone
Having programmed in Go for production a while now, in my experience it's rarely necessary. Sometimes a set is needed, but it's very simple to just use a map[T]struct{}. And if something like union or intersect is needed it's usually less than 20 lines to implement all those operations. Usually that operation is only needed in one instance, and it's very quick to write.
Would it be faster to have a builtin generic set? Absolutely, but it's such a small inconvenience I honestly don't care.
""Social Justice Warrior" Really? That's the level of discourse the author is gonna set the bar at? At least I know that I'm not missing any substance by having just skimmed the post. Seems like a cheap scramble for pageviews with an incredibly biased article, starting with the title."
and
"... presenting an entire post full of loaded language that also rails against "Social Justice Warrior Sarah Sharp's crusade" while claiming to be just "looking at the facts" is disingenuous at best."
But presenting an entire post full of loaded language that also rails against "Social Justice Warrior Sarah Sharp's crusade" while claiming to be just "looking at the facts" is disingenuous at best.
Really? That's the level of discourse the author is gonna set the bar at? At least I know that I'm not missing any substance by having just skimmed the post.
Seems like a cheap scramble for pageviews with an incredibly biased article, starting with the title.