A cautionary tale: not all TreeSets are equal, but some are more equal than others.pic.twitter.com/mMC4bVJFwe
-
In terms of efficiency, that's a reasonable thing to do because the Ordering and an equals method may both be expensive and should probably do the same thing.
But in my real-world use-case I was exploiting this as a convenient way of guaranteeing I never had two elements with the same ID in the same TreeSet (and giving the TreeSet's append method "replace semantics" for free).
-
-
It feels like that should be done by passing in an alternative equals rather than order Feels weird to me
-
I went with a four-line fix which special-cases TreeSet in a pattern match for the one equality check I care about this for. I'm not entirely happy with the solution, but it works.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.