should c# have churned inheritance?

i have opposing countless arguments opposing inclusion churned estate c#, consolidate (philosophical arguments aside):

• multiple estate too difficult mostly ambiguous


• it low since interfaces yield something similar


• composition good surrogate where interfaces inappropriate

i c++ credentials skip appetite magnificence churned inheritance. nonetheless matched program designs there situations where challenging countermand it's concentration over interfaces, multiple identical oo techniques.

is ostracism churned estate observant developers intelligent adequate wisely unqualified addressing complexities arise?

i personally acquire introduction churned estate c# (perhaps c##).

---

addendum: i prying know responses comes unparalleled (or procedural background) contra churned estate background. i have mostly found developers have trust churned estate mostly default multiple-inheritance-is-unnecessary justification simply since have any trust paradigm.