{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihwiayluywjgrolvuxqsz3o2jozo7qhwnjsaf2cqeqn7kqkbtort4",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mfp5vzvvdfp2"
  },
  "path": "/t/pre-rfc-function-parameter-defaults/24011#post_7",
  "publishedAt": "2026-02-25T15:01:58.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "jplatte:\n\n> But you seem to assert that function param defaults only make sense in combination with named parameters, and I think you should make a case to why, rather than just asserting it.\n\nI believe that making defaults always come after the required arguments is a non-starter, because it means that making an argument default, or vice-versa, is a breaking API change.",
  "title": "Pre-RFC: Function parameter defaults"
}