Weihang Lo

For ignoring patches, you can rename the config file to something like `.carog/myconfig.toml` and load it on demand with [`--config` flag](https://doc.rust-lang.org/nightly/cargo/commands/cargo.html#option-cargo---config). It accepts a path to extra config file. For...

This sounds good to me. Once Cargo gets landed and has its own lint control system, we could start rolling out this kind of warning.

From , > If we try again in the future, we will likely try to use the future-incompatible warning system which can report potential breaking in dependencies ahead of time....

Thanks @hanna-kruppe for your reply! Let me see if it is transferrable. @rustbot transfer libs-team

Additional flags passed to `cargo rustdoc` after `--` will go to `rustdoc` invocation. Since Cargo by default sets `--out-dir` already hence such error. I haven't tried but [`--artifact-dir`](https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#artifact-dir) may have...

Due to the lack of `depinfo` files from `rustdoc`, the current rebuild detection relies on [file mtime](https://doc.rust-lang.org/nightly/nightly-rustc/cargo/core/compiler/fingerprint/index.html#rustdoc-mtime-handling) of the final output HTML/JSON files. It might need a more intrusive design...

Would you mind sharing why output final JSON files to stdout is important to your workflow, so that we can understand the use case and brainstorm possible solutions?

Thanks for sharing! If I understand, it is more convenient and predictable if such a flag is provided, but not a hard requirement blocking your development, right? In the meanwhile,...

> > whole rustdoc JSON output for a crate and all its deps to stdout instead of to a file > > Note that flags specified in `cargo rustdoc` only...

Oops the 1.40.0 MSRV is tricky