[chrchr-github]

No description provided.

[danmar]

This is an AI review. Take it with a grain of salt and feel free to reject it by resolving the comment.

The removal looks safe to me. I built the PR and compared it with main on a set of array-to-bool cases (if (buf), if (!buf), bool b = buf;, buf && x, while (buf), buf ? 1 : 2, struct member arrays s->a / s.a) and on samples/, test/cfg/ and a couple of lib/ files with --check-level=exhaustive. The warnings are identical.

One suggestion: valueFlowArrayBool() had explicit handling for a pointer whose tok-value is an array (the isTokValue branch). That case still works after this PR, but I could not find a test covering it in testcondition.cpp. Maybe add a regression test so this doesn't silently break later, for example:

check("void f() {\n"
      "    char buf[10];\n"
      "    char *p = buf;\n"
      "    if (!p) {}\n"
      "}\n");
ASSERT_EQUALS("[test.cpp:4:9]: (style) Condition '!p' is always false [knownConditionTrueFalse]\n", errout_str());

[dmcppcheck]

Test results for commit 5276cfd (tools/test-my-pr.py, main compared to this PR):

Test: http://ec2-16-170-140-253.eu-north-1.compute.amazonaws.com/pr-8905/
packages: 1000
Differing warnings: 0 (+0 -0)
Timing: +0.0% (http://ec2-16-170-140-253.eu-north-1.compute.amazonaws.com/pr-8905/2026-10-01_08-18-36-5276cfdf36c8_timing.html)

_{Posted automatically by the cppcheck PR test runner. +N: warnings only with this PR, -N: warnings only with main. The AI review is written by Claude and can be wrong.}