Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Hmm. I guess the assertion is to silence some tool. And I think actually that function might very well also return null in some cases.
Why do you think it cannot or at least should not return null in your context? I couldn't infer this from the context, neither from the description of this patch.
Without that, I would prefer an if to guard the code, instead of asserting this.
clang/lib/StaticAnalyzer/Checkers/FuchsiaHandleChecker.cpp | ||
---|---|---|
657 | I think there is a typo in the word statement. |
If getStmtForDiagnostics() in general, never returns null, then shouldn't we mark the API with an appropriate attribute?
createBegin() has a call to getValidSourceLocation() which dereferences this Statement. So in this context Statement cannot be null.
If getStmtForDiagnostics() in general, never returns null, then shouldn't we mark the API with an appropriate attribute?
getStmtForDiagnostics() explicitly returns nullptr when none of the cases for ProgramPoint listed in the function are met. So I am not sure if we can just assume this function should never return null.
clang/lib/StaticAnalyzer/Checkers/FuchsiaHandleChecker.cpp | ||
---|---|---|
657 | Thanks for the review. I corrected this in the commit. |
I think there is a typo in the word statement.