It doesn't -- that's the point.
Currently it's assumed that the order base classes appear
in a class statement is the order that they must appear
in the MRO.
It’s not assumed — it’s how order is specified by the coder...
But that's not always true.
Isn’t it true by definition?
I'm suggesting that
the MRO algorithm should not assume that and should make
its own assessment of the required ordering.
Isn’t that impossible? It could determine that order doesn’t matter (no name clashes), but when that’s the case, there’s nothing to do.
What am I missing?
-CHB