Removing `Minimum`?

[xldenis]

Hi, first thanks for the great crate, concurrent-map its nice to have easy access to a battle-tested concurrent ordered map :)

The only wrinkle I have occurs when using ConcurrentMap with external types due to the Minimum trait which causes issues with orphan rules. Looking at the implementation it doesn't look simple to remove the Minimum bound, but perhaps you have thoughts on the subject?

[spacejam]

To avoid orphan issues, you can make a wrapper around a type that you're using from another crate. It's a little bit annoying, but should allow you to achieve the desired result. In addition to implementing Minimum, you can implement Deref so that it still acts like the wrapped type in your code that uses it without a ton of breakage.