cargo-bloat
cargo-bloat copied to clipboard
RazrFalcon
Analyze proc-macro.
What is the use case for this? Wouldn't it conflict when crates have proc-macro dependencies? Have you tried running cargo bloat with this patch on a crate that uses proc-macros?
I find the serde_derive lib is very large, which crate type is a proc-macro.
I tested it on my own side project.
cargo bloat explicitly ignores proc-macros because it looks for binaries and can incorrectly select a proc-macro instead of user's binary. At least we had such a bug.
So I'm not sure this change would work as expected. We have to somehow check that the user actually want to analyze a proc macro. No idea how to implement this thought.