Keep transitive deps that would look optional after pruning about cargo-depgraph HOT 2 OPEN

I think it makes sense for this to be the default behavior of --dedup-transitive-deps, not just for optional dependencies, but target-specific dependencies as well.

from cargo-depgraph.

Yes I agree. Then the question becomes how to handle optional and target-specific dependencies when there is a path of optional/target-specific dependencies (as opposed to a path of required dependencies where the situation is simple).

I think optional deps should still be shown, but target-specific deps can be inferred through each other.

One issue with this could be when a long chain of packages has a similar feature flag to enable one specific dependency (say clap), and then we draw multiple optional lines to that package. On the other hand, drawing the dependency only for the bottom one isn't complete either.

from cargo-depgraph.