I am going to close this. It is always possible to find a static analysis tool that will produce warnings for almost any kind of code. It is not useful work to silence these warnings.

For example, with -Weverything, the following proper code generates a warning:

int main(int argc, char **argv) {
    if (argc != 2) {
        return 0;
    }
    printf("argv[1] = %s\n", argv[1]);
}

(Code taken from StackOverflow.)

Indeed, the static analyser will consider that argv[1] is unsafe. Yet it is perfectly safe and standard code.

That's not reasonable at scale. It might be reasonable for one's own code, but it is not viable within simdjson to avoid pointer accesses.

We support compiling with -Wall -Wextra without warnings. If you need something like -Wunsafe-buffer-usage which generates false positives repeated, you should either accept the warnings in your logs, or silence selectively this warning. Please consult the documentation of your compiler.