On Sunday, 3 January 2016 at 16:44:35 UTC, tsbockman wrote:
If it's a private internal data structure which is only used a
few places, then sure - just use the minimum code required to
get the job done.
But, if it's a part of the public API for a module and the
class logically has a natural ordering, it's better to specify
its behavior once in the class definition, rather than
re-implement it everywhere that needs it.
Yes. I totally agree with you.
In the public API of a module, it can make your life so much
easier if it's reuseable in all useful ways.