Weihang Lo

As of `cargo 1.82.0-nightly (0d8d22f83 2024-08-08)`, the profile rustflags are passed to rustc invocations independently to other existing stable mechanism (`build.rustflags`, `target..rustflags`, `cargo rustc -- `, `RUSTFLAGS` etc.), and has...

By lowest precedence I meant they are passed earlier. Cargo doesn't merge them. Cargo passes them to rustc verbatim. Flags from `-Zprofile-rustflags` are appended first. Then `cargo rustc -- `....

I am going to close this as there is no concrete reproduction for a while. Feel free to opena a new issue when you have a way to reproduce the...

> I'd propose that we reject `--color` and close this as "resolved" with the merge of #13463 That sounds fair. Should we document this unfortunate truth somewhere?

> I untagged it; unsure why github closed it. https://github.com/rust-lang/cargo/pull/13463/commits/67474259e9893fdfa3a9f98148dc871e3c970e31 The close keyword also works in commit messages 😈.

@jtmoon79 thanks for the report. That is a different issue than this. Test harness (by default it's libtest from rustc) usually provide their own way to customize console output. Those...

Cargo hit this issue when importing `rustfix` into `rust-lang/cargo`: . I don't think we want a fix here, but indeed the error message could be better. I am also glad...

Not entirely sure on rustc side of this, but I feel like it is waiting for Cargo to report back the integration status. See also:

+1 for this option on macOS!! I am curious about why this feature need to be ignored on Mac

I am quite interested in the `macro-dependencies` idea. Is the full story in your mind, or could you share a generalized semantic meaning of `macro-dependencies`? (sorry if that is off-topic...