CapeWearingAeroplane ,

I've seen this thing where people dislike inheritance a lot, and I have to admit that I kind of struggle with seeing the issue when it's used appropriately. I write a bunch of models that all share a large amount of core functionality, so of course I write an abstract base class in which a couple methods are overridden by derived models. I think it's beautiful in the way that I can say "This model will do X, Y, Z, as long as there exists an implementation of methods A, B, C, which have these signatures", then I can inherit that base class and implement A, B, and C for a bunch of different cases. In short, I think it's a very useful way to express the purpose of the code, without focusing on the implementation of specific details, and a very natural way of expressing that two classes are closely related models, with the same functionality, as expressed by the base class.

I honestly have a hard time seeing how not using inheritance would make such a code base cleaner, but please tell me, I would love to learn.

  • Alle
  • Abonniert
  • Moderiert
  • Favoriten
  • random
  • linuxmemes@lemmy.world
  • haupteingang
  • Alle Magazine