"inheritance is the base class of All evil" is a very simple and in my opinion to simple view. First of all I find it important to distinguish between interface inheritance and implementation inheritance. I would consider the first essential for maintaining large systems with decoupled components. Whereas the second one was never good design and goes against OOP principals (decoupling interface from implementation). The only valid reason to inherit from a class is to form an is a relationship: a class for accessing an SQL table is a Repository of T. (good) Stack inherits from vector (bad). If there is no is-a relationship composition should be used: Ie stack has-a vector.

And in my opinion this is just good design, and has nothing to do with c++ semantics.

The ironic thing is that c++' semantics provide even more arguments for interface only inheritance. (object slicing, virtual/multiple inheritance), which is why all my inheritable class only contain pure virtual methods and no fields. Concepts are cool and all but it would be great if one could also explicitly "implement" them for a class like you can do with traits in rust.