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.
-
-
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 -
Replying to @BRIAN_____ @sayrer and
How is the build system supposed to know? Does Bazel have a magic Rust parser that can understand comment changes?
2 replies 0 retweets 0 likes -
Replying to @BRIAN_____ @sayrer and
The hash is not the same because doc comments end up in the metadata.
1 reply 0 retweets 2 likes -
Replying to @BRIAN_____ @sayrer and
Also, debug file/line info in DWARF. Yes, I agree there’s room for improvement here. But it’s *compiler* work, not build system work. That’s my entire point.
2 replies 0 retweets 1 like
Doc comment syntax is just syntactic sugar for function attributes, which are written into metadata.
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.