> Comparing language tooling to Rust is surely controversial when compiles in Rust take an order of magnitude longer than any other language.
Do you have any source for that other than a hello world? I always read that both C++ and Rust take about the same amount of time.
Hang on just a sec
Updating crates.io index
Fetch [> ] 0.12%
Re:Talking with the Inventor of C++
by lifthrasiir on Sunday December 03, 2023 @03:34AM
(#38505713)
Cargo is i) not a compiler, and ii) moving to the sparse index protocol [1] that do not fetch the whole index anyway. And even the older git protocol won't fetch the same data twice.
[1] https://doc.rust-lang.org/nightly/cargo/reference/registry-i...
As a fairly avid Rust user I can say I'm excited to hear that! Just playing a little devil's advocate for fun.
That said I was moderately upset by this Friday after carefully assembling a development container for a project at work. Guess I'll have to make something persistent somewhere if I don't want to twiddle my thumbs before each build.
Re:Talking with the Inventor of C++
by lifthrasiir on Sunday December 03, 2023 @01:57PM
(#38509690)
Cargo or not you probably should do that for your container, or use a shared cache (which I do at work for both Cargo and pip) ;-)
Re:Talking with the Inventor of C++
by flykespice on Sunday December 03, 2023 @07:30AM
(#38506591)
> Comparing language tooling to Rust is surely controversial when compiles in Rust take an order of magnitude longer than any other language.
The great benefits brought by having a standard tooling that actually has useful diagnostic and packaging makes any kind of slowdown tolerable.
Unless you code holding your piss.
Comparing language tooling to Rust is surely controversial when compiles in Rust take an order of magnitude longer than any other language. Sure, Rust's tooling has some nice features but let's not ignore this very important elephant in the room.