Lol that’s what I noticed too.

One side wants less people to die, the other side wants fascism and racism. Please help me compromise.

So are you saying that me pushing a pregnant woman down the stairs is the same as doing so to a non pregnant woman?

Imo, no. Pushing a woman is assault, pushing a pregnant woman is assault and something else (another post suggested something akin to manslaughter, which I think fits if the assault causes a miscarriage)

the pro-life response is simply that the unborn child doesn’t get a say in the matter.

Correct. An unborn child doesn’t get a say in whether they are aborted or born. They have no opinions, they have no wants. The unborn child cannot consent to being aborted but they cannot consent to being born either. The only valid opinion and choice is that of the mother, because it’s the mother’s life that is very physically (and eventually also mentally, socially, etc) affected by the pregnancy.

Which is also why I said that pushing a pregnant woman should have harsher penalties than just assault: it also endangers or destroys something whose state of being only the woman should be in charge of.

It’s like if I pickpocket your wallet that’s stealing, but if I steal the wallet from your house that’s also breaking and entering.

I suspect the sarcasm detector of the downvoters might be faulty

Meh. Been developing professionally with C++ for 10 years at this point. I’m one of the weird people that kinda likes C++ and its pragmatism despite all its warts.

I’d like C++ better if it didn’t have inheritance. There are better solutions to model interfaces, and without inheritance people can’t write class hierarchies that are 10 levels deep with a different set of virtual functions overridden (and new virtual functions added) at each level.

And yes, that is not hypothetical. Real codebases in the real world shipping working products do that, and it’s about as nice as you can imagine.

You do have a terminology mismatch. In C++, an abstract class is a class with at least one pure virtual method.

Such classes cannot be instantiated, so they are useful only as base classes.

An interface is more of a concept than a thing.

Sure you can say that Iterable is an interface that provides the Next() and Prev() methods and you can say that Array is an Iterable because it inherits from Iterable (and then you override those methods to do the correct thing), and that’s one way to implement an interface in C++.

But you can also say that Iterable<T> is a class template that provides a Next() and Prev() methods that call the methods of the same name on the type that they wrap (CRTP aka static polymorphism).

Or you can say that an algorithm that scans a collection T forward requires the collection to have a Next() method by calling Next() on it.

And I can think of at least 2 other ways to define an interface that isn’t using abstract classes.

And even if using abstract classes, inheriting from them is definitely the least flexible way to use them to define an interface, because it doesn’t allow one to do something like mocking functionality in tests, because it’s not possible to redefine the class to be tested to inherit from the test interface implementation with mocked functionality, so one still needs something to the effect of dependency injection anyway.

So yeah, abstract class is very different from inheritance, and it’s also very different from interface, even though it relates to both.