Eric Huss

@kamathba Can you clarify some things about your use case for me? I'm trying to understand why you are using `--out-dir` at all. Are you manually setting the list of...

@Lokathor Can you share a minimum example to demonstrate? I'm not sure how to reproduce your issue. Also, which platform are you on?

@Lokathor OK, I see what is happening. It is a consequence of having cdylib and `panic="abort"` with an integration test and a binary. For reasons, cdylibs don't have a unique...

@SimonSapin It is a bug. This won't become a hard error until most of the bugs are resolved. Part of the reason of this warning is to ferret out these...

> is there a way to select which one of the colliding packages should be used in the doc Unfortunately, no. The one that appears in the final output can...

@SimonSapin Can you explain which situation generated that message with `cargo doc`? I have updated the message for some of the other situations to make it clearer it is a...

Case-sensitivity in rustdoc is tracked in https://github.com/rust-lang/rust/issues/25879. It's not something Cargo can do anything about (it doesn't parse Rust or have any insight into the structure of the code).

Linking issue #8941, which notes a problem with fingerprinting duplicate executables in a workspace.

The `doc = false` is a target setting (goes under `[[bin]]`), not a package setting (see [here](https://doc.rust-lang.org/cargo/reference/cargo-targets.html#configuring-a-target)).

There are two copies of `fst` in your dependency graph. There is the root fst, and then the one from crates.io (from various dependencies, such as fst-bin and regex-automata). They...