{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiazzuzy65zbx2d6ltupujxarx5rrf44gdhhxkgkjssi5rhemduxvq",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mphnotb5eeh2"
  },
  "path": "/t/code-compiles-on-playground-but-fails-when-passed-via-stdin-to-rustc/24393?page=2#post_35",
  "publishedAt": "2026-06-29T20:58:03.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "MusicalNinjaDad:\n\n> and question whether `CARGO_UNSTABLE_ALLOW_FEATURES` should remain the more common approach given `-Zallow-features` now exists\n\nIt's the other way around, `rustc -Zallow-features` has existed for years longer than `cargo -Zallow-features` (but I'm pretty sure that is also years old at this point). The latter is a superset of the former, it controls both cargo and rustc unstable features, and has a much better UX for shared workspace definitions in its TOML form.",
  "title": "Code compiles on playground but fails when passed via stdin to rustc"
}