https://youtrack.jetbrains.com/issue/KT-39406 If you agree with what I’m saying a thumbs up on the issue would be greatly appreciated
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.
I have a case here.