Greg

Note that the current naming is `--disallow_analysis_cache_discards` in reference to https://github.com/bazelbuild/bazel/pull/16805#issuecomment-1496233870. I'm not going to take any further position on flag naming (that vs. the later suggestions) and will approve...

I think this is ready to land aside from landing the final flag name and vetting the failed presubmit checks. If @mattem is busy would anyone else like to carry...

Awesome! Do you happen to have a recap of the latest diff compared to before this week? Just trying to refresh my memory.

I thought we had a similar challenge with the original merge somewhere? If so, it should be straightforward to resolve. I'll get to this as soon as I can. What's...

Yes. I was away for two weeks, just back today. I'll try to prep up a new patch...

I'm a bit lost in the conversation history here and at https://github.com/bazelbuild/bazel/pull/13587. I didn't fully follow Case 3. For example, can you elaborate "This has the unwanted consequence that E...

> > I didn't fully follow Case 3. For example, can you elaborate "This has the unwanted consequence that E can no longer be a dependency of D"? > >...

> This proposed rule (all actions generating a given file in a single build must be identical) is looser than the current rule in Bazel master (only one action may...

C++ actions aren't shareable because of include scanning: finding dependencies by reading `#include ` in source files. That creates a mutable dependency graph: some dependencies are added (or even removed)...

@torgil this is complicated and long-standing because the issue is fundamentally complicated. And it's not a single issue: it's a related collection of issues with varying levels of support and...