How should we render features?

[epage]

Currently, its:

features:
    name = [activation1, activation2, ...]

We could render this as a tree:

features:
  parent1
    child1
  parent2
    child1*

If we track activations, we could do a hybrid where explicit activations (see rust-lang/cargo#10681) are always roots and inactive features are processed like a normal tree

features:
  default
    default-dep1
    default-dep2
  other
  default-dep2*
  disabled1
  disabled2    

The question then is how to handle activations

• Currently, default is the only thing activated
• For cargo add: Show features that were explicitly enabled rust-lang/cargo#10681 , we'd need to choose a package (from parent directory?) to identify activations from the dependency entry
• Alternatively, we could check the feature resolution and just show whatever is default activated for the workspace (ie what cargo-metadata would treat as activated)

[epage]

If we leverage activations, either kind, we could then mark a dependency as optional or required based on that.