cgeo/c-geo-opensource — comment on commit bc5309a0c0797eabaac834d971d27298fa8d786e
File:  line 0
By Bananeweizen:

I'm completely fine with your arguments. What I meant to say is: If I work with a list in an API, then I don't even need to think about what I'm doing, because that is often used standard stuff. When I suddenly get a Set by an API, then I need to put my brain into a higher gear, because some of the "usual" things aren't valid anymore. Like I somehow iterate the set and my output in the app is no longer sorted, although I created it from some other sorted collection. So at least for me the Set is the collection kind where I tend to make something wrong more easily (and I guess, I wouldn't have thought about the equals and hashCode implementation, too). And therefore I sometimes try to encapsulate such a surprising class by a more known class. But that might be completely impossible and/or useless in this case.