{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifms4jzku4ikqlpzyzhieueb2v3nlodpan5nihhee4id2g66ac4wy",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mo2chzha5xx2"
  },
  "path": "/t/pre-rfc-explicit-overload-sets-for-mixed-arity-function-calls/24372#post_18",
  "publishedAt": "2026-06-11T21:34:58.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "If this is purely for FFI, then to me, the obvious way to solve the problem is for functions to have different names on the two sides of the FFI boundary: on the Rust side of the boundary, all the overloads of a given C++ function would have their own individual names, but on the C++ side they would all have the same name, with the `extern` block specifying the mapping between them.\n\nThat would avoid any complication in Rust the language: the only additional complication from the overloads would be about writing the `extern` block, as it would need to specify both names.",
  "title": "Pre-RFC: Explicit overload sets for mixed-arity function calls"
}