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

I think you argue that people can have good taste when it comes to overloads. The problem with good taste is that it can't be enforced by a linter (at least not yet) and it doesn't scale. And as soon as you have a project with hundreds of developers that becomes unenforceable both socially and from a review workload point of view. The answer is thus to just not do overloading at all, it is just a feature too prone to be misused for bad API design, as we see time and again in C++. Rust should as far as possible nudge people in the direction of "good" code, and it does a pretty decent job at that currently. C++ as a language really doesn't. There are books and lists on all the parts of C++ you shouldn't use any more. Rust for the most part doesn't need that (yet?). Overloading would be a major step in the wrong direction for Rust.