Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • TLDR: "do not inherit implementation". Has nothing to do with the question. Commented Feb 18 at 13:20
  • @Basilevs, it's more like "do not use class inheritance as a solo developer" and "providing one level of class inheritance is already a lot", so the premises of the question evaporate. The OPs example of an "inelegant" (yet quite simple) solution is in fact a minor overhead completely appropriate to the rarity of the circumstances and the illegitimacy of "scaling" that approach. Commented Feb 18 at 14:20