go doesn't have inheritance it just has composition, where you write the name of a parent class inside a child class, and get all its fields and methods but yo

go doesn't have inheritance it just has composition, where you write the name of a parent class inside a child class, and get all its fields and methods but you don't inherit them, and unlike some languages you type the parent's name inside the class rather than in the typedecl generics? we won't need them. okay yes maybe not having generics will lead to an outcome where it is impossible to publish reusable code for sorting and lists, but surely if we gave people generics they would simply abuse them and live in filth there should be a name for the type of language designer who thinks you can give people generics without ruining the package ecosystem it is Good and Right that most lines of code are `if x, err := thing(); err { return err }`. from a language design perspective, manually plumbing errors around prevents Pollution of the package ecosystem. we can Lint the % of tokens that are `err` and if the % is low that is a bad language to which ours is superior