> Maybe we should reject the unary case in anticipation of an RoR overload.

Maybe. Could be ambiguous though. I'm always a bit cautious about adding overloads to a function that accepts varargs. For example, why not provide a setIntersection for `RoRs...` ?