3 ms·
This depends on what the library does, of course. From a quick Google I believe the parent has made several packages, like a front-end to help with XML trees or
by jeroenhd 5y ago
This depends on what the library does, of course. From a quick Google I believe the parent has made several packages, like a front-end to help with XML trees or a full wrapper around procfs. Libraries that complex (especially with their dependencies) can take significant time to compile, it's just a consequence of their complexity.
Some smaller libraries I've seen that just do some annoying-to-test but simple string manipulations have had similar compile times, mostly because they include specific versions of advanced logging or error reporting libraries for no obvious reason.
- eminence32 5y agoYup, that's me :) For example in the `procfs` crate, there's a dependency on `flate2` just in case a /boot/config.gz file exists (in order to see what options the kernel was built with). But if a consumer never needs to inspect the kernel options, this dependency (and related code) is just dead-weight. The nice thing about rust is that this code will be removed from the final executable if it's unused, but maybe it's time to start thinking more carefully about compile times.