Ramon Leon wrote:
> Traits can be composed better because you can specify which methods you want
> from conflicting traits explicitly.  Ruby's modules I believe don't allow
> you to mix and match, but is based on inclusion order only.

Do you have an example for this? I'm uncertain what a "conflicting 
trait" is and how this would be resolved (in either implementation).

Cheers,
   - Andreas