{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiddqvt5vecgwsy5iyooytneghfcggxy27dnvl5y3xyyheqthwhewy",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mnuq4fv2ief2"
  },
  "path": "/t/pre-rfc-explicit-overload-sets-for-mixed-arity-function-calls/24372#post_10",
  "publishedAt": "2026-06-09T16:37:36.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "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.\n\nFurthermore, 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.",
  "title": "Pre-RFC: Explicit overload sets for mixed-arity function calls"
}