> the compiler will flag all pattern matches that you need to update

At Google, the bottleneck is that a team changing a commonly used enum will not know how to update all the broken use sites, since it can be affecting dozens or hundreds of teams.

It is better to decouple the enum change from the use site change and let consuming teams update on their own schedule.

I am not familiar with this flag, but will it force, or at least alert these " consuming teams" that the enum they expected has changed?

No, but Google already has internal tools that can identify use sites and email affected teams.

Note that teams generally manage their own deployments, so even a repo wide code change doesn’t force the update of an older deployed binary.

Everything that you say can be true, and yet Asahi project may want to avoid needing to prove what you say in a courtroom.

"We don't want to take on the risk of working with a former Apple employee, who could potentially leak trade secrets and expose us to unwanted liability" is a very different statement than asserting that they were banned for deception. The post you're replying to is responding to accusations against their character and behaviour. Clearing those up is an entirely different matter than saying anything about whether former employees should be allowed to contribute to the project.

> attempt to reduce wealth inequality is a sign itself that it's a very wealthy country

Poor countries also reduce wealth inequality. In fact, China went through a Communist revolution where all private landowners’ wealth was taken from them. This happened from the 1930s through the 1950s and was a fairly bloody, violent process, involving lots of revolutionaries inciting peasants to forcibly occupy land and buildings and killing landlords if they didn’t cooperate.