{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicxkpa5qscrqf2x5n63kqsmrpqmqf6woja6dos24gyas5nivasfom",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mnjcvkmnod22"
  },
  "path": "/t/pre-rfc-explicit-overload-sets-for-mixed-arity-function-calls/24372#post_2",
  "publishedAt": "2026-06-05T04:25:50.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "I continue to be opposed to anything that just adds a need for overload resolution rules. We have trait resolution rules already; that's enough. I never want to have to think about both trait resolution _and_ overload resolution.\n\nCheck zulip -- there are people talking about ways to have a single function delegate to a single _trait_ via a tuple or similar, which seems fine.\n\nIn the mean time, you can always just do\n\n\n    draw((point));\n    draw((x, y));\n\n\nas ordinary function calls and it's fine.",
  "title": "Pre-RFC: Explicit overload sets for mixed-arity function calls"
}