{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreialrmtrybknfmym37y3zwzr666r2mzcyh2wczpk5lbnbrmmrwm3iy",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mjviujmrvbs2"
  },
  "path": "/t/pre-rfc-pub-api-visibility-and-static-enforcement-of-crate-internal-api-boundaries/24184#post_4",
  "publishedAt": "2026-04-20T02:38:07.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "unreachable_pub"
  ],
  "textContent": "I thought that, generally, all pub items are suggested to be exported from the containing crate. The text of the unreachable_pub rustc lint docs say:\n\n> This lint is “allow” by default because it will trigger for a large amount of existing Rust code. Eventually it is desired for this to become warn-by-default.\n\nI don't see it saying that pub methods are an exception here (at least when it's in warn mode).\n\nRegardless, I can work through that example again, either replacing it or at least mentioning it as another example.",
  "title": "Pre-RFC: `pub(api)` visibility, and static enforcement of crate-internal API boundaries"
}