That's a good point. It's one of the things that confused me about trait stacking when I first started learning Scala. People often effectively use traits to im

That's a good point. It's one of the things that confused me about trait stacking when I first started learning Scala. People often effectively use traits to implement composition, in the sense that the intention isn't that you would take advantage of Liskov substitution, but rather you intend to aggregate behavior from a number of sources. It's one of many ways in Scala where a single abstract construct could have several different semantics applied to it.