[clang] [clang][analyzer] Improve checker 'unix.cstring.NotNullTerminated' (PR #149106)

[Balazs Benics via cfe-commits]

=?utf-8?q?Balázs_Kéri?= <balazs.keri at ericsson.com>
Message-ID:
In-Reply-To: <llvm.org/llvm/llvm-project/pull/149106 at github.com>


steakhal wrote:

I frequently see you and @NagyDonat fighting clang-format. Let me share what I use in my workflow.
I use VSCode, but this should work with any editor. Usually editors have hooks for file saves.
I use the [Run on Save](https://marketplace.visualstudio.com/items?itemName=emeraldwalk.RunOnSave) extension, with the following hook:
```json
{
    "emeraldwalk.runonsave": {
        "commands": [
            {
                "match": "\\.(c|cpp|h|hpp)$",
                "isAsync": true,
                "cmd": "bash -c \"export PATH=\\\"/myclanginstall/clang-18/bin:$PATH\\\"; git clang-format --force\""
            }
        ]
    }
}
```

After every time I hit "save", it reshuffles the code that I touch, but nothing else. Its awesome. Let me know if you found this useful.

https://github.com/llvm/llvm-project/pull/149106