4 ms·
On top of this, there's this bogus mantra in the Rust community that "if it type checks then it works." I've spent of hours interactively debugging Rust code,
by duped 3y ago
On top of this, there's this bogus mantra in the Rust community that "if it type checks then it works."
I've spent of hours interactively debugging Rust code, crawling through tracing output etc, and hours waiting for Rust code to link with mold because I added an eprintln somewhere, so I'm not convinced.
I love writing Rust and think it makes my life easier, but there's this stockholm syndrome about compile times. It sucks, and it's not the type system or borrowchecker's fault.
- mrkeen 3y ago> there's this stockholm syndrome about compile times. It sucks, and it's not the type system or borrowchecker's fault. What do you mean?
- duped 3y agoThe bottlenecks in Rust builds arent't type checking/borrow checking. It's things like macro expansion, module resolution and compilation, codegen from LLVM IR, and linking. Some of these things have workarounds like sccache, using mold instead of the system linker, etc but others are problems that not only remain unsolved but are actively getting worse in the ecosystem.
- dralley 3y ago>hours waiting for Rust code to link with mold because I added an eprintln somewhere How is that Rust's fault?
- saghm 3y agoI think the "with mold" comment is expressing that even with the state-of-the-art fastest linker that's generally available for use with Rust, it still is slow. If you used the default linker, it would be even slower.