Somewhat surprisingly, the #rust API for working with sets pushes you towards a double negative: to test whether a set has an intersection, you do
!set_a.is_disjoint(&set_b);
I would have thought that it'd be better API design to implement a `has_intersection` method (or similar) which avoids the ! and "dis" double negative.
I wonder why they went this way?
(And, yeah, there would be ways to avoid the double negative, but all are pretty clunky)
@codesections I agree, since the intersection of two sets is always garunteed to have unique itoms and there will never be duplicity then a Set makes way more sense than a list.