Default test binary

[PSeitz]

It would be nice to bloat check the default cargo test binary. It would allow to analyze bloat to reduce compile times.

You could also do a release build, that would probably cover more than some superficial binary. There would be some noise due to dev-dependencies though.

Similar to #67

[RazrFalcon]

cargo bloat isn't really useful to reduce compilation times. And checking bloat of tests is mostly pointless as well.
cargo bloat is useful only when checking release builds of executables.

[PSeitz]

cargo bloat isn't really useful to reduce compilation times.

Your reddit post would suggest otherwise :)
https://old.reddit.com/r/rust/comments/cg3p5m/cargobloat_08_debloated_5x_smaller_10x_faster/

And checking bloat of tests is mostly pointless as well.

I have to clean my rust projects regularly, because the fill up my disk >100GB.
E.g. one test binary is 267MB large and I'm just wondering, which crates to attribute it to.

[RazrFalcon]

Your reddit post would suggest otherwise

That post it 4 years old. You have to use cargo build --timings instead.

E.g. one test binary is 267MB large and I'm just wondering, which crates to attribute it to.

cargo bloat doesn't check build artifacts, only the final binary. It a very different statistics.

Also, aren't you already can check tests? Simply use cargo bloat --test NAME. Not sure how hard would be to detect the "default test".

[kpreid]

Also, aren't you already can check tests? Simply use cargo bloat --test NAME. Not sure how hard would be to detect the "default test".

All kinds of non-test targets can be built as test binaries, and those can't be addressed via --test. I believe you have to use specifically cargo test --no-run to build the test binaries, though there might be another way I don’t know.