A top-level root profile for overriding dev and release profiles simultaneously #10953
Labels
A-profiles
Area: profiles
C-feature-request
Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Problem
Currently, if you have some profile that needs to always apply regardless of whether the crate is being built in release mode or not, you're required to specify the options twice, once for dev mode and once for release mode:
Proposed Solution
Since profile inheritance is already a concept, it would be nice if the
dev
andrelease
profiles inherited from aroot
profile so that bothdev
andrelease
could be overridden together:Notes
According to the Zulip thread here: https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/profile.20wildcards/near/281732406 , the name "root" is already reserved for this purpose.
The text was updated successfully, but these errors were encountered: