# Multiple Inheritance Support

**URL:** <https://discuss.kotlinlang.org/t/multiple-inheritance-support/17974>\
**Category:** Language Design\
**Created:** [June 5, 2020, 8:39am UTC](https://discuss.kotlinlang.org/t/multiple-inheritance-support/17974 "2020-06-05T08:39:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![darksnake](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.kotlinlang.org/darksnake/32/2479_2.png) [@darksnake](https://discuss.kotlinlang.org/u/darksnake)\
**Post date:** [June 5, 2020, 9:02am UTC](https://discuss.kotlinlang.org/t/multiple-inheritance-support/17974/2 "2020-06-05T09:02:06Z")

</div>

I do not think that multiple inheritance is a technical problem. It could be solved easily the same way it is done for interfaces with default methods. I think that the existence of multiple inheritance allows for some rather unpleasant practices which could be avoided. You should support your case with some examples where you really need it.

The class hierarchies, where you inherit only functions could be done right now via interfaces and extensions, you can actually even emulate multiple inheritance for fields via kotlin properties. If you actually have a field in two ancestors, you are definitely doing something wrong.

---

_[View the full topic](https://discuss.kotlinlang.org/t/multiple-inheritance-support/17974)._