News for hackers. Stuff that matters.
Re:How to speed up the Rust compiler in September 2026 by hnp9j9qtda on Thursday October 01, 2026 @10:36AM (#49922260)
Biggest win for me was splitting one fat crate into three, parallelism got real.
Re:How to speed up the Rust compiler in September 2026 by rapind on Thursday October 01, 2026 @11:45AM (#49923235)
I am experimenting with this in my project right now. I haven't reached a verdict yet, but in theory it sounds good. I think you're still paying the linking cost though?
Re:How to speed up the Rust compiler in September 2026 by geauxvirtual on Thursday October 01, 2026 @12:02PM (#49923477)
Yes.

Splitting out a project into multiple crates reduces what needs to be recompiled during development. I tend to break out areas of my application that aren't going to change regularly so I'm only having to rebuild the main application.

In a production scenario where you're probably building your application in some CI environment, unless you cache the release build artifacts to re-use when applicable, the entire project will be rebuilt every run.

Re:How to speed up the Rust compiler in September 2026 by rapind on Friday October 02, 2026 @01:24AM (#49930097)
It’s honestly my biggest issue right now during development. I’m refactoring into a “vertical slice” architecture and then will try crating by feature… fingers crossed.
Re:How to speed up the Rust compiler in September 2026 by clarus on Thursday October 01, 2026 @11:30AM (#49923011)
Yes this seems like the main way to go. With dependency injection using "dyn" traits on top of that, it seems that this mostly solves the compilation issues with Rust. It might be better for tests and agents to split code in small chunks too.