4 ms·
I don't see the problem. Since it's an external crate, it will compile exactly once after adding it to Cargo.toml, and will be cached forever.
by axiosgunnar 5y ago
I don't see the problem. Since it's an external crate, it will compile exactly once after adding it to Cargo.toml, and will be cached forever.
- unanswered 5y agoI'm convinced that most of the people complaining about build times are using docker for some incomprehensible reason and are blowing away the dependency cache with every build.
- rowanG077 5y agoThis. It's annoying to compile from scratch. But I almost never have to do that. So I don't really have a problem with compile times.
- nicoburns 5y agoNope. FWIW, I conpile on a MacBook. So I only have 2 cores, and laptop ones at that. Perhaps that's affecting our difference in perspective? I also had a project a couple of years ago where I had to compile it in release mode to get reasonable performance for testing (Iw as processing GB's of data), which meant 2-3min incremental compile times. Not fun!
- kzrdude 5y agoforever, or until rust version update (might be often for nightly builds), or until build flag change or cargo clean, whichever happens first. It's also only a per-project target directory (not across all projects you compile).
- kibwen 5y agoEven for people on nightly builds of the compiler, I would be quite surprised if nearly anyone actually bothered to upgrade their compiler every night. Most people on nightly are just going to be there for the use of a specific unstable feature.
- finnb 5y agoCached locally, sure. The point of bazel with remote execution and remote caching is that it's then available in the cloud for everyone to access.