feat(profile): Add built-in profile debug #17214
Open
epage wants to merge 3 commits into
Open
Conversation
Key points: - It inherits from `dev` - Conceptually, debugging is part of the development process - The hope is this will smooth out the transition for people - `cargo install --debug` now uses `debug` instead of `dev` - `debug` changes nothing from `dev` right now. `dev` will evolve in the future (with `debug` overriding those values to leave it effectively unchanged) but that is deferred out to offer a transition period where `debug` can be used without but isn't required for debugging as people deal with multiple Rust versions. This also shrinks the change and decouples what the conversation around what the settings should be.
Collaborator
|
r? @ehuss rustbot has assigned @ehuss. Use Why was this reviewer chosen?The reviewer was selected based on:
|
rustbot
added
A-documenting-cargo-itself
Draft
epage
marked this pull request as ready for review
July 15, 2026 00:10
rustbot
added
the
S-waiting-on-review
Collaborator
|
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
Member
|
Should we include the meeting note in the PR description? |
Contributor
Author
|
Added the link and what looked like I might have been missing |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR try to resolve?
Key points:
devcargo install --debugnow usesdebuginstead ofdevdebugchanges nothing fromdevright now.devwill evolve in the future(with
debugoverriding those values to leave it effectively unchanged)but that is deferred out to offer a transition period where
debugcan be used without but isn't required for debugging as people deal
with multiple Rust versions. This also shrinks the change and
decouples what the conversation around what the settings should be.
devstill usestarget/debug: this does not change any calculation for the transition cost and any conflicts between the profiles should mostly be in the artifact-dir (which are just hard links), especially once the new build layout lands--dev/--debugflags are deferred out, needing more evaluation to decide if they are worth itSee also https://github.com/rust-lang/cargo-team/blob/main/meetings/sync-meeting/2026-07-14.md#splitting-dev-and-debug-profiles
How to test and review this PR?
This is part of #15931
build.profilewill be a follow up (Config profile #17215)devprofile changes are deferred for 1+ releases