{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifk6jgf6xlq5ucudjhsz5sd3zb75wuudlihesormt5w65wza263tm",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkqsraszekg2"
  },
  "path": "/t/pre-rfc-btf-relocations/24161?page=2#post_22",
  "publishedAt": "2026-04-30T23:50:25.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "Does it have to be a feature of structs and arrays?\n\nCould it instead be expressed as a macro or intrinsic function that gives an offset to use with `ptr::read`? (which could be sufficient to make getters and setters for something struct-like that isn't an actual struct)\n\nOr maybe it could be implemented as getters and setters on extern opaque types?\n\nIt wouldn't be as neat as 1st class structs that work with literals and pattern matching, but might be sufficient to interact with kernel structs treating them as an API.",
  "title": "[Pre-RFC] BTF relocations"
}