| Issue |
115620
|
| Summary |
[clang-tidy] figure out if an iteration is actually problematic in `bugprone-nondeterministic-pointer-iteration-order`
|
| Labels |
clang-tidy,
false-positive
|
| Assignees |
|
| Reporter |
5chmidti
|
https://clang.llvm.org/extra/clang-tidy/checks/bugprone/nondeterministic-pointer-iteration-order.html
> This check currently does not check if a nondeterministic iteration order is likely to be a mistake, and instead marks all such iterations as bugprone.
As stated in https://github.com/llvm/llvm-project/pull/110471#issuecomment-2400972013, `Expr::hasSideEffects` may be an easy and quick way to determine if there is an observable effect (e.g., I/O). It would be good, if in the end, the check would detect, e.g., string concatenation but ignore commutative operations (e.g., accumulate).
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
