Cargo should support configuration in non-hidden files.

[jrvanwhy]

Describe the problem you are trying to solve

Currently, cargo searches for configuration files by looking for a directory named .cargo, which is a hidden directory. This means that a typical ls invocation does not reveal the existence of a config file. This makes it difficult to debug problems caused by cargo config files, particularly for contributors who are new to a project.

Describe the solution you'd like

I would like Cargo to search for a config file in a non-hidden location, such as cargo/config. This way projects that want to use Cargo configs and make that config visible can do so.

Alternative idea in case searching in a new location is considered a breaking change: We could add a field to Cargo.toml pointing to the Cargo config to use when invoked from within a particular crate or workspace.

Notes

The Tock project uses Makefiles to pass flags to rustc and the linker rather than using a cargo config because they do not want to have any configs in hidden files.

[jrvanwhy]

Adding @ppannuto from the Tock project.

[ppannuto]

It's not just ls, the majority of tools (find, grep, etc) will ignore hidden files.

Putting critical build configuration in files that standard tools will not find makes discovery very challenging for new and even experienced users. Particularly in embedded systems contexts, non-trivial compiler customization is often necessary, and it's important that how targets are configured be easily visible.

From our experiences with TinyOS, using any hidden files to drive configuration is a non-starter for Tock.

[malaire]

I agree. The Cargo.toml is not hidden and so requiring .cargo/config to be hidden is not consistent.

[epage]

Generally, when I see projects do this, they use a _ prefix instead to sort these "semi-hidden" files and directories separately from the rest.

: We could add a field to Cargo.toml pointing to the Cargo config to use when invoked from within a particular crate or workspace.

Config files are environment configuation, distinct from project configuration, see #12738