[clang] [analyzer] Use explicit call description mode in iterator checkers (PR #88913)

https://github.com/NagyDonat closed https://github.com/llvm/llvm-project/pull/88913 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[clang] [analyzer] Use explicit call description mode in iterator checkers (PR #88913)

NagyDonat wrote: Uh oh, those niebloids are really deep black magic :skull_and_crossbones: I didn't know about them previously, so thanks for mentioning them. https://github.com/llvm/llvm-project/pull/88913 ___ cfe-commits mailing list

[clang] [analyzer] Use explicit call description mode in iterator checkers (PR #88913)

https://github.com/steakhal approved this pull request. This should be all good. FYI std lib funcs are not always functions. They could be also niebloids, which we cant actually hook. This shouldnt affect these apis though. I left it here as food for thought.

[clang] [analyzer] Use explicit call description mode in iterator checkers (PR #88913)

llvmbot wrote: @llvm/pr-subscribers-clang @llvm/pr-subscribers-clang-static-analyzer-1 Author: None (NagyDonat) Changes This commit explicitly specifies the matching mode (C library function, any non-method function, or C++ method) for the `CallDescription`s constructed in the

[clang] [analyzer] Use explicit call description mode in iterator checkers (PR #88913)

https://github.com/NagyDonat created https://github.com/llvm/llvm-project/pull/88913 This commit explicitly specifies the matching mode (C library function, any non-method function, or C++ method) for the `CallDescription`s constructed in the iterator/container checkers. This change won't