There's a proverb in these here parts that goes like "He who doesn't want to kneed dough, keeps sifting flour".
Perhaps a modern dev-friendly version would be, "He who doesn't want to code, keeps configuring their text editor".
That seems to be the case with Generics and the endless "documents" and "analysis" in Go. If you don't particularly want to do something, you keep analyzing different ways of doing it...
Most of these "analyses" especially from Ian has backing code changes.
This for example, is my experiment with trying to give Go a backing calculus that supports generics https://asciinema.org/a/166748
The runtime changes yielded over 20k lines of changes - basically about 1/4th of the Go runtime has to change. Not to mention a large amount of semantics changed too - essentially a different language
>The runtime changes yielded over 20k lines of changes - basically about 1/4th of the Go runtime has to change. Not to mention a large amount of semantics changed too
Well, isn't it a major typesystem change? Makes sense for it to apply to a big part of the runtime and semantics.
Perhaps a modern dev-friendly version would be, "He who doesn't want to code, keeps configuring their text editor".
That seems to be the case with Generics and the endless "documents" and "analysis" in Go. If you don't particularly want to do something, you keep analyzing different ways of doing it...