-
-
From my experience, cargo will detect an out of date input file and invoke rustc on the http://lib.rs/main.rs only, at that point I assume the compiler has some smarts as to what it needs to recompile wrt what changed. Any dependents of a rebuilt crate would then also rebuild.
1 reply 0 retweets 0 likes -
Replying to @peterhuene @jntrnr and
So, let's assume two files: http://main.rs and http://a.rs . http://main.rs is using fn a(x: i32), defined in http://a.rs . If I now change the return value for a(), would http://main.rs be recompiled?
1 reply 0 retweets 0 likes -
Replying to @ArvidGerstmann @peterhuene and
Since the interface hasn't changed, http://main.rs wouldn't need to recompile (and if this were C, for example, would definitely not recompile). But since the distinction between interface & implementation is quite blurred in rust, I'm questioning this.
2 replies 0 retweets 0 likes -
Replying to @ArvidGerstmann @peterhuene and
*this* is talking about changes within the same crate. Rust will, as of fairly recently (6 months? A year?) only re-compile the bits that changed, and stuff that depends on the bits that changed.
1 reply 0 retweets 3 likes
This is called “incremental recompilation”. And we have more work to do there; it’s not perfect yet
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.