Cargo could be smarter about its default rustc arguments when rustc is used

[nagisa]

While I was debuging a certain code generation issue reported against rustc, I wanted to disable debug info generation, because it together with -C lto makes rustc ICE. Was surprised when I got back a following error.

$ cargo rustc -- -C lto -C debuginfo=0
   Compiling vim_updater v1.0.0 (file:///tmp/collectionScripts/rust/vim_updater)
error: -g and -C debuginfo both provided

[stale]

As there hasn't been any activity here in a while would someone (the author, a team member, or any interested party) be able to summarise the current state, perhaps making explicit:

• Is this still relevant?
• If so, what is blocking it?
• Is it known what could be done to help move this forward?

Thank you!

(The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.)

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

[stale]

As I didn't see any updates in 30 days I'm going to close this. Please see the previous comment for more information!