One of the good thing in cargo packages are the feature flags. If a repo uses too much dependencies then it's time to open an issue or PR to hide them behind fe

One of the good thing in cargo packages are the feature flags. If a repo uses too much dependencies then it's time to open an issue or PR to hide them behind feature flags. I do that a lot with packages that requires std even though it could do with core and alloc. cargo tree helps a lot on viewing dependency tree. I forgot if it does LoC count or not.. > to see what lines ACTUALLY get compiled into the final binary, This doesn't really make much sense as a lot of the functions that make it to the binary get inlined so much that it often becomes part of 'main' function