{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihtqdut22guxolz3icininrlixtt342mywd2uks52lqm5rzydot7i",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mgutbxztiqf2"
  },
  "path": "/t/optional-features-are-part-of-the-crate-the-project-should-say-so/24069#post_16",
  "publishedAt": "2026-03-12T16:12:28.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "tomveens:\n\n> A hint from cargo.toml for rust-analyzer can be used to include optional features. But for that to make sense it should also benefit Cargo, and I don't know enough about Cargo's design to say if that's justified.\n\nI think that `default-features-for-development` would benefit Cargo workflows, too. In particular, if `cargo test` enabled those features by default, then `cargo test` without arguments would be closer to “test everything reasonable”, instead of the status quo of not testing anything that’s an optional feature not enabled by anything in the workspace.",
  "title": "Optional features are part of the crate — the project should say so"
}