From clang-tidy – cppcoreguidelines-pro-bounds-pointer-arithmetic: Pointers should only refer to single objects, and pointer arithmetic is fragile and easy to get wrong. span<T> is a bounds-checked, safe type for accessing arrays of data. So yes: Is there an alternative way to use the values of argv without using pointer arithmetic? Isn’t accessing a char** by any … Read more
I found a solution: false positives (like the Apple singleton design pattern) can be avoided with: #ifndef __clang_analyzer__ // Code not to be analyzed #endif Analyzer will not analyze the code between those preprocessor directives.
I ran into this issue as well, and spent some time trying to figure it out, but I could not see a way to disable this type of warning in clang-tidy. From reading this discussion on the LLVM issue tracker regarding a similar issue, I get the impression that the problem is that from clang-tidy’s … Read more
The way to do what’s expected is shown in listing 3-5 in that document. With your example code: + (NSString *)checkForLength: (NSString *)theString error: (NSError **)error { BOOL hasLength = ([theString length] > 0); if (hasLength) return theString; else { if (error != NULL) *error = [NSError errorWithDomain:@”ErrorDomain” code:hasLength userInfo:nil]; return nil; } }