{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibcih3avm6fhzgvb6e6z3qawqzqvtosrtt553cig6nn5nxna66h5y",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mfukbjs73kn2"
  },
  "path": "/t/pre-pre-rfc-splatting-for-named-arguments-and-function-overloading/24012?page=3#post_42",
  "publishedAt": "2026-02-26T20:09:58.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "Oh, I didn't mean to say \"I don't want Rust-to-Rust overloading\", just \"it's not a goal of mine to get that\".\n\nWhere I'm coming from is: \"tiny syntactic sugar gets us pretty nice FFI powers and also extends to named arguments which we wanted anyways\". I love it when we get a lot of benefit for not much design complexity, something about this \"fits well\" in the language to my taste.\n\nI don't mind that this gives a Rust-to-Rust overloading feature. I'm sure some ppl will find APIs where this is really beneficial to have and the rest won't bother with the weird trait dances required.",
  "title": "[Pre-pre-RFC] \"splatting\" for named arguments and function overloading"
}