Comment by alpaca128
10 months ago
Build times have nothing to do with cargo but with the language itself. They're not the "price to easy", it's the price of the static compiler checks.
10 months ago
Build times have nothing to do with cargo but with the language itself. They're not the "price to easy", it's the price of the static compiler checks.
Isn’t it the price of the LLVM backend? That would make it a rustc implementation price.
that's only true if you believe dependency resolution is free.
I have never witnessed cargo being delayed from that by a noteworthy amount of time.
I just tried it, on my PC it takes cargo 0.3 seconds to start compiling the first of 309 dependencies in a clean Bevy repo. The entire compilation takes 31 seconds, and that's the best case with lots of multithreading and all packages already downloaded. That's close enough to "free" for me.
doesn't really matter. You said "nothing to do with" and I said "is not free".
1/3 of a second for a build that has already cached all dependencies means I was correct that it's not free and you were being dismissive when you said it had nothing to do with build times.
If you want to argue that it's a minimal amount of time then argue that instead of what you've been arguing.
2 replies →
Cargo does not do dependency resolution on every build.
how does a dependency management system ensure the dependencies are there without doing dependency resolution?
2 replies →