Pre-RFC: Explicit overload sets for mixed-arity function calls

That is just an argument for bad API design of the STL. It is not an argument against this feature, unless you argue that it's not possible to create a good API with overloads. Furthermore, even if this is what you argue, in large existing C++ projects that had a large API surface area overloads are just a fact, and coming with new names for every overloaded method is a huge burden. Then you also have to maintain those names when the API changes.