3 ms·
Re: modulo compiler performance My productivity has been greatly improved by restricting myself to `cargo check` when writing code. It only does type and borro
by dikaiosune 11y ago
Re: modulo compiler performance
My productivity has been greatly improved by restricting myself to `cargo check` when writing code. It only does type and borrow checking which is much faster than doing all of the LLVM passes (or whatever rustc does after those passes, on that subject I am ignorant).
- Manishearth 11y agoNote that even for large codebase, the Go compile is faster than Rust up to typecheck. Not much faster, but when I use Go I get errors immediately; whereas in Rust I often context-switch to wait for errors (both for large codebases). Some planned improvements to Rust may fix this.
- dikaiosune 11y agoFair enough, and being honest I haven't tried Go yet so I have no basis for comparison between the two compilers. I've found that when using Atom with linter/linter-rust installed and setup with cargo check I rarely context switch while waiting for errors/warnings to be highlighted (and this is on a 1.6Ghz Xeon machine at work). But maybe I'm just OK staring blankly for slightly longer than others :).
- Manishearth 11y agoWell, I work with really large codebases in Rust (Servo or Rust itself), so the twenty seconds to a compile error are a lot. Whereas when hacking on Go's compiler it's much, much less.