Comment by norir
10 months ago
There is a price to easy. In my experience, cargo build times tend to be soulkillingly long. But I don't like waiting more than a few hundred ms for incremental builds. So for me, cargo build is actually harder than make to attain an enjoyable build system.
Make is annoying but Makefile issues are found quickly and easily when running `find . | entr -c make` and saving the source file often.
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.
3 replies →
Cargo does not do dependency resolution on every build.
3 replies →