7 ms·
still compiles too slowly, a language in 2016 just cannot take multiple seconds for me to use it add 5 crates and watch ur compile/run cycle climb to a cool 10+
by hubert123 10y ago
still compiles too slowly, a language in 2016 just cannot take multiple seconds for me to use it
add 5 crates and watch ur compile/run cycle climb to a cool 10+ second average.
- steveklabnik 10y agoWe had significant compile-time improvements in the release yesterday, with more to come in the future. Also, you might want to give incremental recompilation a try, it's nightly-only for now, but being actively worked on. > add 5 crates and watch ur compile/run cycle climb to a cool 10+ second average. It should not recompile those crates each time, if it does, that's a bug. Please report them!
- coolsunglasses 10y agoJust to litmus test this, I rebuilt a small Rust project of mine that depends on 41 crates. Debug build took 15 seconds, release build took 37 seconds. Rebuilds are sub-second. This is 0.15 nightly. TBQH, Rust's release builds are already faster than GHC's -O0 builds for me. I'm still bereft a REPL (I live in a REPL), but it's not a deal-breaker.
- nnethercote 10y ago> It should not recompile those crates each time, if it does, that's a bug. Please report them! Depends on the inter-crate dependencies, alas. Touching one crate can easily cause multiple other crates to rebuild.
- steveklabnik 10y agoOnly if you need to modify both crates; not if you're just adding them as dependencies, because then you're not modifying them. I was assuming that's what the parent was doing, due to their wording, but that might have been a bad assumption.
- computerphage 10y agoIncremental compilation is stabilizing on Nightly. It won't help the initial compile, but waiting even 5-10 Minutes when I start working on a new codebase doesn't really matter to me. It's only the incremental speed that I care about.