It is currently possible to have a pin without a corresponding dependency, to simplify manifest edition. These crates are considered implicit dependencies for the solver, and show as such in alr with --solve. However, they are not considered by other informative commands like with --graph, with --tree, or simply with, because these rely exclusively on explicit dependencies returned by Release.Dependencies.

It's probably more in line with user expectations to show the implicit dependency introduced by a pin in all these commands.

The obvious solution seems to add an extra paramenter to the dependency-retrieval function that considers Pins when they don't already have a dependency. In that case, a new User_Pins.As_Dependency would be the proper place to generate one.