The `dev` profile serves double duty: - faster iteration time - debugger support These come into conflict with some settings for debuggers slowing down builds, with potential changes to values like - [`debug`](https://doc.rust-lang.org/cargo/reference/profiles.html#debug) - [`opt-level`](https://doc.rust-lang.org/cargo/reference/profiles.html#opt-level) See also - #10481 - https://blog.rust-lang.org/inside-rust/2024/12/13/this-development-cycle-in-cargo-1.84/#improving-the-built-in-profiles - https://internals.rust-lang.org/t/feedback-request-performance-improvements-from-reducing-debug-info/21825 - [#t-cargo > Effect of disabling debuginfo in the dev profile @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/246057-t-cargo/topic/Effect.20of.20disabling.20debuginfo.20in.20the.20dev.20profile/near/493805868) - [#t-cargo > `-Csplit-debuginfo=unpacked` on Linux @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/246057-t-cargo/topic/.60-Csplit-debuginfo.3Dunpacked.60.20on.20Linux/near/307639121) - https://blog.rust-lang.org/2024/02/19/2023-Rust-Annual-Survey-2023-results.html#challenges has build times and debugging as neck and neck - https://mas.to/@davidlattimore/113484821980790635
The
devprofile serves double duty:These come into conflict with some settings for debuggers slowing down builds, with potential changes to values like
debugopt-levelSee also