1,068 karma · joined January 6, 2012
On the other hand, we just saw The Green Knight and that one will throw you.
Does it? I'm not familiar with Go data science applications but the design of the language, tooling and runtime, eg low latency garbage collector, errors thrown for unused imports, do not, to me, seem to fit well with the needs of data science. I'm interested in hearing what advantages Go brings.
For the record, if Trump called up Maggie Haberman and gave an on-the-record interview, I'm sure that would get covered too!
I guarantee you that if he called into Fox, his comments would be carried by every media outlet and discussed exhaustively on Twitter.
"Resolving that requires effectively unbounded lookahead. In general we strive to keep the Go parser simple."
It's totally fair to question the tradeoff - should having a simple parser outweigh the potential ergonomic benefit of <>? I don't know. The forum for this is probably the golang-nuts group.
Also note that generic methods are not allowed in the current design, only generic functions.
The new draft design ( https://go.googlesource.com/proposal/+/refs/heads/master/des... ) discusses both of these points. I recommend everyone who is interested in this topic read the design spec, ideally before commenting.