Git-ignoring the `.cargo` folder?

[tombh]

I have some fancy nightly features I like to enable for faster compiles, but they live in .cargo/config.toml. The trouble is that they depend on my specific CPU architecture, so they can't be committed to any repo. Here's an example:

# See: https://bevyengine.org/learn/quick-start/getting-started/setup

# Find your machines arch with `rustc -vV | sed -n 's|host: ||p'`
[target.aarch64-unknown-linux-gnu]
linker = "clang"
rustflags = [
  "-C", "link-arg=-fuse-ld=/usr/bin/mold",
  # (Nightly) Make the current crate share its generic instantiations
  "-Zshare-generics=y"
]

# Don't forget to:
# `rustup component add rustc-codegen-cranelift-preview --toolchain nightly`
[unstable]
codegen-backend = true
[profile.dev]
codegen-backend = "cranelift"
[profile.dev.package."*"]
codegen-backend = "llvm"

In this repo we use .cargo/config.toml for a xtask alias, so I can't add all those fancy nightly flags. I'd personally vote for ignoring the .cargo folder, but it's not a big deal, so I'm just making an issue to register my vote.

[schell]

Could you possibly put your personal configuration file further up in the hierarchy of config files?

For example you maybe you could wrap the cargo-gpu repo in another directory, say rust-gpu-projects and then add your config.toml to that directory?

I would prefer to keep .cargo/config.toml tracked as I often add other things to it (env vars, for example).