4 ms·
I think it is unfair to call this document biased, from the document: > This document is a distillation of convoluted generics discussions and it is not an off
by mijoharas 12y ago
I think it is unfair to call this document biased, from the document:
> This document is a distillation of convoluted generics discussions and it is not an official opinion of the Go team, although it does incorporate their opinions.
I think the document simply amalgamates all the points that have been made on both sides of the debate. I would agree that some of the points made against the generics do seem to be somewhat biased (or debatable or flimsy/whatever), but I think the document itself merely tries to collect all of these arguments together, so that when someone says, "what is the argument against this point?", people can point to this document and say that someone raised the argument that "The generic structures are less useful than a concrete one". I think then that can be used as the starting point for discussion (someone can raise the counterpoint that they think this is wrong).
I see this as separating the discussion of the validity of the points from an enumeration of the points made so that people can refer to them (which I think is helpful). In addition, with all the arguments for and against collected together, people can more effectively discuss the proposition.
EDIT: I am all for go having generics, I just don't think the document itself is biased.