Skip to content

Allow to find out easy way what feature was enabled in transient in crate and what not #45

@dzmitry-lahoda

Description

@dzmitry-lahoda

I usually do

  1. Look into Cargo.lock

cargo check --verbose --job 1 --unit-graph -Z unstable-options 
  1. cargo tree

I have the case

  1. A has std feature.
  2. It uses B having std, sure when A has std.
  3. B uses C. C has std too. But be forgot to enable std on C.
  4. So when I compile A, it fails, because we are in std feature, but C did not enabled it.

In some codebase it hard to debug - when there are dozens of crates in several layers with several adhoc features (I work at such). I use above tooling.

Would be awesome to have some oneliner to see all features in crates, why they are enabled or not.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions