Why is it hard (or even non-pathologically possible) for the CI system to do the right thing here? CI is choked because builds take a long time, typically.
-
-
It is very much not the case that changing a .md file in the docs causes an LLVM rebuild. This has *NEVER* been the case in Rust’s 10 year history.
1 reply 0 retweets 1 like -
Nor is it the case that changing a .rs file in the compiler causes an LLVM rebuild. Again, this has *never* been the case.
1 reply 0 retweets 1 like -
So if LLVM is being rebuilt when the docs change, it is a problem specific to the CI, and it should be solved *there*. Because if you change the build system to Bazel, and don’t fix *that* issue, it will *still* be a problem.
1 reply 0 retweets 2 likes -
This Tweet is unavailable.
-
Now we’re getting somewhere. The reason why that triggered a rebuild is that the compiler couldn’t tell—or, more likely, incremental compilation lacked the hooks to tell the build system—that a rebuild was not necessary.
1 reply 0 retweets 0 likes -
This is a problem that needs to be solved! But it needs to be solved *in the compiler*. The problem is presumably that the compiler, right now, can’t say “oh, I didn’t need to rebuild anything” in a way that the build system can understand.
3 replies 0 retweets 1 like -
Why can’t the build system look at the pending inputs and cached outputs and avoid even asking the compiler in the first place. With the FB Android app, if you ran javac you’d already lost, so to get real wins you have to avoid running the compiler, aggressively.
1 reply 0 retweets 1 like -
The build system sees a .rs file change. That change could potentially invalidate everything. It would have to be able to parse Rust to know that it’s a comment change.
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
*Every* file is potentially downstream from that one. If you change libcore/future/future.rs then you potentially invalidate every single artifact. It’s libcore.
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.