Maybe it is just revealing where those programmers are coming from. Java and C++? Angle brackets! Eiffel, Scala? Square brackets!
Are there any parser considerations (like <Foo <Bar>> being an issue in C++, afair), or is it just taste (or Scala vs. C++ background)?
This line of code seems to say why is troublesome given Go's other syntax:
a, b = w < x, y > (z)Used to be, a long time ago.
a < b
a [ b
It may be easier to branch in one of those cases instead of the other.
Not at all familiar with the potential issues (if any) in go, but this is from experience in writing a few languages.
Yes, in fact I can point to two different cases related to usage of angled brackets for generics:
1) Typescript claims to be a superset of JS, but it isn't, precisely because of this. `a<b,c>(d)` parses as a call to `a(d)` in TS, but parses to two comparisons in JS
2) D explicitly chose `!(foo)` syntax for templates over the `<foo>` syntax in order to avoid the parsing ambiguities problem