Benjamin,
Obviously, I have wanted to go this route all along. I don't know if this will ever happen in Dart though. The benefits of such a design are maximized if it comes in on day one. We would have no need for libraries, imports, dependency injection etc. if we did this up front. But Dart is more conservative, and did not go this route. At this stage, any design will have to deal with legacy in the language, libraries and implementations.
There are still benefits of course. We have encountered interesting scenarios where class hierarchy inheritance would be very valuable for example, and I've spoken about those in academic forums. I wrote up a proposal for extensible libraries, which could be seen as subset of this functionality designed specifically to support class hierarchy inheritance. I will update it and turn it into a DEP sometime. However, I would not hold my breath :-(