Mutable methods for all data structures

[orium]

These can use {Rc,Arc}::make_mut() that can speed up things a lot if there is not a lot of structural sharing.

• List
  • impl
  • utests
  • bench
• Vector
  • impl
  • utests
  • bench
• Stack
  • impl
  • utests
• Queue
  • impl
  • utests
• HashTrieMap
  • impl
  • utests
  • bench
• HashTrieSet
  • impl
  • utests
• RedBlackTreeMap
  • impl
  • utests
  • bench
• RedBlackTreeSet
  • impl
  • utests
• Run clippy
• Update README.md

[Marwes]

2c

I am not convinced about the split into mut/non-mut structures. Keeping all the methods on a single structure is both simpler to implement and easier to use. The only pro I can see for keeping it separate is that it makes it more explicit when mutating is done, however since Rust already forces the user to be explicit about mutating that is already encoded at the call site.

[orium]

My main motivation for the separation is conceptual (having neat API, separation of two different paradigms). But I have to say that the maintenance burden of doing this separation starts to outweight the conceptual neatness I was looking for. I will follow your suggestion and not split them.