{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreie6nedwlekbmthowuilm7jrsvpye7gjuqzjsrgja32ilzo4omi3h4",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3moshvy5hao22"
  },
  "path": "/t/code-compiles-on-playground-but-fails-when-passed-via-stdin-to-rustc/24393#post_17",
  "publishedAt": "2026-06-21T13:01:41.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "programmerjake:\n\n> IMO Rust never guaranteed it wouldn't add more warnings for code that was warning-free, so if you use `deny(warnings)`, you're opting-in to breakage.\n\nYes, and probes really _should_ aim to use a specific `#[forbid(...)]` etc. to change the specific case they are testing.\n\nAnd yet ... In this case we are looking at potentially breaking build scripts _silently_ with hard-to-spot and hard-to-debug consequences, not only for the crate in question but for _anyone downstream_ and without any action needed on anyone's part (other than updating rustc) for the breakage to occur.\n\nSo, while I agree that \"you really shouldn't have done that, so you have no-one else to blame\" is the _technically right_ call, I also don't feel comfortable putting an MCP in for this without a thumbs-up form someone more senior.",
  "title": "Code compiles on playground but fails when passed via stdin to rustc"
}