Allow setting Cargo flags (e.g., -Zbuild-std) per profile

[ProgrammedInsanity]

Problem

It would be great if we could specify flags like -Zbuild-std for individual profiles in Cargo.toml, instead of creating aliases or global config. This would provide more flexibility, especially when specific configurations are needed for development or release builds. It would also eliminate the need for different aliases for building, running, benchmarks, and tests, allowing us to simply specify --profile .....

Proposed Solution

Example

[profile.release]
cargoflags = [" -Zbuild-std"]

Notes

No response

[epage]

It would also eliminate the need for different aliases for building, running, benchmarks, and tests, allowing us to simply specify --profile .....

Instead of cargo check -Zbuild-std, you can do cargo -Zbuild-std check. You can then create a single alias

[alias]
z = "-Zbuild-std"

and run commands like

cargo z check

Or you can be like me and have a shell alias. Mine is called nargo so I can do nargo check.

You can also set -Z flags in config which can also be set in the environment or through --config.

[epage]

It would be great if we could specify flags like -Zbuild-std for individual profiles in Cargo.toml, instead of creating aliases or global config.

Unstable features require an explicit opt-in. We could claim this new profile is just that but for myself, I'd prefer a central field for simplicity / reduced risk. In this way the solution would be

cargo-features = ["profile-cargo-features"]

# ...

[profile.release]
cargo-flags = ["-Zbuild-std']