{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidfa7u6z5epakirvjwzggvtv6tmtg6xwxj4ppw6jthyeqxvayifai",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mostlibmjze2"
  },
  "path": "/t/code-compiles-on-playground-but-fails-when-passed-via-stdin-to-rustc/24393#post_18",
  "publishedAt": "2026-06-21T14:00:20.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "Provide a way for build scripts to invoke rustc the way cargo would · Issue #11244 · rust-lang/cargo · GitHub"
  ],
  "textContent": "MusicalNinjaDad:\n\n> My worry would be `autocfg`. If anyone has probes with a leading `#[deny(warnings)]` then that could break with rather nasty consequences\n\nUnsure about T-compiler but T-cargo has decided to not support build probes, see Provide a way for build scripts to invoke rustc the way cargo would · Issue #11244 · rust-lang/cargo · GitHub\n\nWithout Cargo support, build probes have some gotchas.\n\nAlso, for fully general build probes, like `autocfg`, the edïtion should be set. The caller has to do this currently. We've approved telling build scripts the edition but it is unclear if that might get superseded by a compiler feature.",
  "title": "Code compiles on playground but fails when passed via stdin to rustc"
}