{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifqdj7l7xfdag53rdtgtzpq6lltgclrskv4irueg4f23dxlremtui",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mh23gy4uejo2"
  },
  "path": "/t/optional-features-are-part-of-the-crate-the-project-should-say-so/24069?page=2#post_25",
  "publishedAt": "2026-03-14T18:35:59.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "doc.rust-lang.org",
    "Configuration format - Configuration - The Cargo Book"
  ],
  "textContent": "zackw:\n\n> What would be so bad about moving everything, and I really do mean _everything_ , from `.cargo/config.toml` to `Cargo.toml`, _right now,_ so that we can deprecate the _existence_ of `.cargo/config.toml` in packages and workspaces as soon as possible?\n\nI'd recommend actually looking at the config before making such broad statements\n\ndoc.rust-lang.org\n\n### Configuration format - Configuration - The Cargo Book\n\nThis document explains how Cargo’s configuration system works, as well as available keys or configuration. For configuration of a package through its manifest, see the manifest format.\n\n  * alias: there is no manifest lookup for these today\n  * build: half of these are caller, machine, or user specific\n  * credential-alias: user specific\n  * doc: user or machine specific\n  * env: unenumerable use case\n  * future-incompat-report: user specific\n  * cache: user or machine specific\n  * cargo-new: user as the point is that you aren't in a repo\n  * http: user or machine specific\n  * install: caller, user, or machine specific\n  * net: ditto\n  * patch: already in manifest\n  * profile: ditto\n  * resolver: controlled by `workspace.resolver`. Maybe more can go in but design work is needed\n  * registries: unsure\n  * source: ditto\n  * target links: overriding build scripts should likely not be in a static file\n  * term: caller, user, or machine specific\n\n\n\nAnother problem is RUSTFLAGS is a raw escape hatch that users can shoot themselves in the foot with and so it needs a \"here be dragons\" rather than having a paved path in the manifest,",
  "title": "Optional features are part of the crate — the project should say so"
}