{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibt7nj7ghnep5cvkgmbputkyyktoaoa2rute7ha3mszslkxnagn2q",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mnuwtvwavfd2"
  },
  "path": "/t/pre-rfc-explicit-overload-sets-for-mixed-arity-function-calls/24372#post_11",
  "publishedAt": "2026-06-09T18:13:31.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "chrefr:\n\n> unless you argue that it's not possible to create a good API with overloads.\n\nI actually _do_ argue that the costs of ad-hoc overloads are always too high, especially when those ad-hoc overloads are used as extension points.\n\nA variadic _trait_ method that thus can take different arities? Sure, that's fine, because it's not _ad-hoc_.",
  "title": "Pre-RFC: Explicit overload sets for mixed-arity function calls"
}