3 ms·
Part of the reason the compile-edit-test loop is slower than in other languages is because Rust is doing a whole borrow checking phase other languages don't. I
by ModernMech 2mo ago
Part of the reason the compile-edit-test loop is slower than in other languages is because Rust is doing a whole borrow checking phase other languages don't. I don't see why it'd be faster or more accurate to get an LLM to do the same static analysis as the Rust compiler. Although I'd be interested in an analysis of how much each would cost in dollars.
- bombela 2mo agoIt's the compilation that is slow, not the checking. You can observe this by comparing "cargo check" and "cargo build".
- ModernMech 2mo agocargo clean cargo check Finished `dev` profile [unoptimized + debuginfo] target(s) in 2m 40s cargo build Finished `dev` profile [unoptimized + debuginfo] target(s) in 3m 12s cargo clean cargo build Finished `dev` profile [unoptimized + debuginfo] target(s) in 3m 15s shrug
- bombela 2mo agoAnd the difference is more useful in the more common scenario of editing code and checking it. Though those days, language servers like rust-analyzer do essentially replace cargo check. Taking the alacritty project and modifying the source files to pretend something happened: > cargo clean Removed 1602 files, 545.8MiB total > cargo check [...] Finished `dev` profile [unoptimized + debuginfo] target(s) in 17.12s > cargo build [...] Finished `dev` profile [unoptimized + debuginfo] target(s) in 23.04s > find alacritty_terminal/ -name "*.rs" | xargs-I{} sh -c 'echo >> "{}"' > cargo check [...] Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.00s > cargo build [...] Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.37s I wish it was faster, but I will take the speedup that I can!