3 ms·
There's an important point here, which somehow got lost in that article. For Rust, it's important that unsuccessful compiles be fast. Development usually involv
by Animats 3y ago
There's an important point here, which somehow got lost in that article. For Rust, it's important that unsuccessful compiles be fast. Development usually involves far more failed compiles than successful ones, as you satisfy all the consistency conditions which Rust enforces. When the program finally compiles, there's a good chance it will work.
So it's important to benchmark compiles with errors, and make sure those are fast.
One-minute incremental release compiles seem typical. There have been some problems with the optimizer in the linker taking huge amounts of memory if you turn on all the optimizations. A 32GB or larger machine may be needed for some programs.
- ivanjermakov 3y ago> Development usually involves far more failed compiles than successful ones This is less true when using LSP.
- Animats 3y agoLSP just does local syntax. Not cross-module checks, including the borrow checker. The Rust compiler catches local syntax errors very quickly, so that's not a big issue.
- ivanjermakov 3y agoModern LSP servers are capable of workspace-level diagnostics, from my experience with tsserver and rustanalyzer. Had no issues with borrow checker or async checks.