{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibpyphmaagjzj7xvc7qh5dekgmby5rnsbswwiwnv5s7y2kd3um4cm",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mpdqhb4g4by2"
  },
  "path": "/t/code-compiles-on-playground-but-fails-when-passed-via-stdin-to-rustc/24393?page=2#post_25",
  "publishedAt": "2026-06-27T11:51:51.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "RUSTC_OVERRIDE_VERSION_STRING"
  ],
  "textContent": "Nemo157:\n\n> I almost think it would be a good thing to break `autocfg` occasionally and try to influence people away from using it. I run into crates that have issues working on nightly over, and over, _and over_ because of bad auto-detection. I would really like a way to just say \"I'm on at least the latest stable when you were published, use all those features\" and bypass any attempt at detecting for MSRV's I don't care about or unstable features _I do not want used_.\n\nI wish we had proper cargo support for build probes (or something else that alleviates the need for build probes) so people wouldn't have to write their own hacks to substitute for lack of official support. But, well, everyone only has finite capacity so here we are.\n\nThere is an env var you can set which makes `rustc -vV` claim that this is \"stable\" even if you are on nightly; this will disable most of this kind of auto-detection (and it's very clearly a bug in the ones that do not get disabled): RUSTC_OVERRIDE_VERSION_STRING.",
  "title": "Code compiles on playground but fails when passed via stdin to rustc"
}