Repository navigation
Uncomment debug in Cargo.toml - #27261
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## main #27261 +/- ##
==========================================
+ Coverage 83.34% 83.55% +0.21%
==========================================
Files 1173 1173
Lines 479350 485203 +5853
Branches 479350 485203 +5853
==========================================
+ Hits 399501 405407 +5906
+ Misses 55428 55380 -48
+ Partials 24421 24416 -5 see 19 files with indirect coverage changes 🚀 New features to boost your workflow:
|
|
I had committed this change accidentally. 👍 for quickly reverting back to what was there. Doesn't have to be part of this PR, but I'm wondering if a second "interactive development" profile would be useful since stripping most debug information makes interactive debugging unusable. Or perhaps have the 'fast for ai' profile be a dedicated one that the agent is instructed to prefer over 'dev' via agenst.md? |
|
Just did some investigation about what other big Rust open-source projects do:
So it looks to me that adding a second profile specific for debugging is actually a good idea, something like: [profile.dbg]
inherits = "dev"
debug = trueI can add it here 👍 |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Important
Fork CI setup: For pull requests from a fork to
main, enable workflows in your fork's Actions tab before you push.See the fork CI setup guide.
Which issue does this PR close?
Rationale for this change
Just reverts an incidental change from #26155.
What changes are included in this PR?
Uncommenting one intentionally committed line
What is the testing strategy for this PR?
Just a Cargo.toml change
Are there any user-facing changes?
No