102
The Tragic Death of Inheritance (avivcarmi.com)
submitted 3 years ago by to c/programming@programming.dev
52 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 3 years ago (2 children)

C++ dev with minimal experience of composition here, but this is a great article and it's something I've been trying to play with more and more. Out of curiosity, does anyone know if there are any known big pitfalls to avoid with composition (thinking of things like the diamond problem)?

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 4 points 3 years ago* (1 child)

    The only thing I can think of: you often need to strike a balance between having interfaces that are too generic/large or too specific/small. However, you already have to worry about that in OOP (God Object vs ravioli code) so it's not a huge deal.

    Another reply suggested giving Rust a try, and I do second that. But if it's not your cup of tea, at least take a look at some of the standard library traits - std::io::Read/Write and std::iter::Iterator will give you a good idea of what composition can do.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •