[PATCH] D83961: [Analyzer] Fix bug report source locations in minimal output.
Artem Dergachev via Phabricator via cfe-commits
cfe-commits at lists.llvm.org
Tue Jul 28 01:17:37 PDT 2020
NoQ added a comment.
I believe i clarified above how this checker should work. For testing purposes (which is the only reason to ever use the minimal output) i prefer to have it at the end of path, because that tells more about the bug path and therefore more important to test.
The question i'm asking is more about API contracts of the `PathSensitiveBugReport` class over its virtual methods. Right now i don't care whether the entire system behaves correctly or not. I want you to explain how the change in one component caused a change in another component, so that to avoid introducing pairs of mutually cancelling bugs. In other words, this is a unit-test question, not an integration-test question.
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D83961/new/
https://reviews.llvm.org/D83961
More information about the cfe-commits
mailing list