{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreig5dhfvaylstwh2rexkuk47abnbtcnlbkmjdxsqurvhn6efsuyi3e",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mfppt7dpamk2"
  },
  "path": "/t/method-auto-de-ref-and-lack-of-it-in-rfc-132-ufcs/24005#post_7",
  "publishedAt": "2026-02-25T19:44:57.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "but not impossible."
  ],
  "textContent": "bettertree:\n\n> you (and I, initially) seem to have made the mistake of forgetting to add `&` in `Foo::foo(var)`\n\nThere was no mistake, it's a demonstration that introducing auto-ref to non-method coercions can result in calling different functions.\n\nIf it only applied to receivers with qualified paths that include the implementing type, so the target type is known... well... it's a lot harder to demonstrate that inserting auto-ref can change semantics, but not impossible. Probably no one relies on it?",
  "title": "Method auto-(de)ref (and lack of it) in RFC 132 ufcs"
}