uber-go
dig "trace" mode
Currently, we don't get any visibility into the types injected in the DI container of Dig. i.e. it's not really possible to see which constructors' provided types are the "most used" and where the "hot path"s are. Note that what I mean by "hot path" here isn't code that's executed frequently - each constructor in Dig is invoked precisely once. The "hot path" here is the constructor where the most of the graph depends on.
Also this may be useful for identifying types that are provided but aren't really used anywhere, which may help users identify some dead code, or break down constructors that aren't used frequently, etc.
what's difference of "trace" mod and Visualize function which can generates a DOT file used for graphviz
i think the result of Visualize function now is not elegant and clear, i think it could be designed as you mentioned