News for hackers. Stuff that matters.
Re:Rust 1.5 by pjc50 on Thursday December 10, 2015 @11:26AM (#10711447)
How long is "long"? What sort of time would we be talking about for 100KLOC projects?
Re:Rust 1.5 by jmquigs on Thursday December 10, 2015 @02:28PM (#10712780)
I don't know about 100K, but for my 5667 line project, a recent nightly build takes 8 seconds to build on my 2012 macbook pro (4 core 2.3G i7). That is with up-to-date external crates that aren't being rebuilt.

Typecheck happens early, with borrow-checking following soon after, so you get feedback on errors fast, and thus only end up waiting when the compiler is happy with your code. Still, it may be an issue for people who like to do TDD or need to do a lot of run-time verification.

For a big project you'd probably need to split it up into multiple crates to "emulate" incremental compilation, at least until it is supported by the build system.

Re:Rust 1.5 by steveklabnik on Thursday December 10, 2015 @03:19PM (#10713150)
That exact property is why cargo check works.
Re:Rust 1.5 by jamwt on Thursday December 10, 2015 @05:17PM (#10713961)
You would definitely split that project up into multiple crates at the moment. 100KLOC would take an eternity to compile. My guess would be 15 to 45 minutes for a release build, depending on things like how much you were using generics.