{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiabt7fkmxemc7dqzyj2vd6qw76o4yrb5igevkbt7u2ew5mbgmomoe",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mfuqyvzivgd2"
  },
  "path": "/t/pre-pre-rfc-splatting-for-named-arguments-and-function-overloading/24012?page=3#post_41",
  "publishedAt": "2026-02-26T15:29:37.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "Nadrieril:\n\n> You can only splat a generic that implements `Tuple`, which is only implemented for built-in tuples, so only the crate that defines the trait can define impls for it, unless I'm forgetting some piece of orphan rules magic.\n\nI… somehow overlooked that restriction when writing that section of my post. So yes, the orphan rules for `impl ForeiegnTrait for (…)` are at least as restrictive as `impl ForeiegnTrait<(…)> for ForeiegnType`, which is what I suggested as an alternative.",
  "title": "[Pre-pre-RFC] \"splatting\" for named arguments and function overloading"
}