It's then up to consumers of the crate to know that they probably should disable features they aren't using, to save pulling in lots of unnecessary dependencies.
Whilst this reduces the confusion/friction for people who don't know how to enable a Cargo feature (since everything works out of the box), its very rare that anyone needs all features, so literally every consumer should really switch to default-features = false eventually.
Lots of consumers of the crate aren't doing this (even those maintained by experienced Rust users), eg:
By default
libherokubuildpackhas all Cargo features enabled: https://github.com/heroku/libcnb.rs/blob/d2b747520b1d66dc29716ffba1b0f13fcef6952d/libherokubuildpack/Cargo.toml#L21It's then up to consumers of the crate to know that they probably should disable features they aren't using, to save pulling in lots of unnecessary dependencies.
Whilst this reduces the confusion/friction for people who don't know how to enable a Cargo feature (since everything works out of the box), its very rare that anyone needs all features, so literally every consumer should really switch to
default-features = falseeventually.Lots of consumers of the crate aren't doing this (even those maintained by experienced Rust users), eg:
And even the ones that are, often are doing so only because I fixed them:
We should either not enable any features by default, or only enable the most commonly used ones (eg logging).