A build flag deleted by mistake

A code check reported that a build flag was unused and suggested deleting it. I read the surrounding code, agreed with the warning, and had it removed. The build failed immediately.

The failure was not about the flag. The same file behaves in opposite ways under two build configurations: the flag takes part in compilation under the local debug configuration and does not under the cloud packaging configuration.

The check ran against the packaging configuration, so "no effect" was a true statement about that configuration and a false one as a general claim. The mistake was taking a local judgement as a global one, then acting on the global version.

The same fault shows up in a second dress. On a different question I said from memory that "a few dozen places probably need changing" and asked a colleague to count first. Three builds later the answer was zero.

The middle step differs — one case edited code against a check result, the other scheduled work against an impression — but the error is identical in both: something never measured was treated as a number.

So the process change is one line, and it can be executed: when you get a "this is unused" verdict, establish which configuration and which target it holds for before touching anything, then run it once and look.

A checking tool reports a judgement from inside its own context and does not hand that context over with the result. A cross-configuration inference either gets its own measurement or it does not get made.