{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicwpk225zbfdw5msczzqhb55ivetellltbtutn2q3urhy7ohiegsm",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mgs3zj2tqfv2"
  },
  "path": "/t/optional-features-are-part-of-the-crate-the-project-should-say-so/24069#post_7",
  "publishedAt": "2026-03-11T14:15:04.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "The configuration is more directed to the editor. So we must use config files for each editor. I wish to version control that analysis can be done even over certain optional features. I don't the editor is using, I actually don't want to care. I do know that the rust-analyser is more important, and I don't like to setup over and over again for every editor. Rust-analyser does have the feature. They also already use the cargo config. I think it is a project specific setting and not a editor one. Keeps my git clean.  And I stumbled upon it because, setting it in the zed editor did not work -> so me thinking what could be better.",
  "title": "Optional features are part of the crate — the project should say so"
}