It is no secret that language limits both what we can think and express. When you can only think in terms of single inheritance, it deeply changes how you structure your object model. The reason is that when folks perform OOAD, they pretty much never look at the implementation language as a “runtime” on which to implement and deploy, instead they look at it as “how you can think”. Sure you can model a system with multiple inheritance, but you never do, because you know you will end up using a single inheritance language.

> This is probably officially a ’sharp knife’ so be careful with this kind of programming. It can be non-intuitive
> to people and can probably be greatly overused but it is a very valuable tool in many cases.

You should try this out and go overboard. How else could you really get a good feel for how well it lets you grow the language into something powerful and useful? The mistakes made using this approach would be infinitely more valuable than the small-ish examples of its application.