gribozavr added inline comments.
================
Comment at:
clang/include/clang/StaticAnalyzer/Core/BugReporter/BugReporter.h:350
+
+ llvm::ArrayRef<FixItHint> getFixits() const { return Fixits; }
+
----------------
No need to qualify with "llvm::".
================
Comment at:
clang/include/clang/StaticAnalyzer/Core/BugReporter/BugReporter.h:491
+ ArrayRef<SourceRange> Ranges = None,
+ ArrayRef<FixItHint> Fixits = None);
----------------
I'm not sure if this is the right model for fixits. Fixits are usually
associated with a message that explains what the fixit does. Only in the
unusual case where Clang or ClangTidy is very confident that the fixit is
correct, it is attached to the warning. Most commonly, fixits are attached to
notes.
Also, for IDE support, it would be really nice if we could provide short
descriptions of edits themselves (e.g., "replace 'virtual' with 'override")
that can be displayed to the user instead of the diff when possible -- right
now we don't and tools using ClangTidy have to use a subpar UI because of that.
For example, when we show UI for fixing a warning, displaying the complete diff
is too much; a concise description would be a lot better.
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D65182/new/
https://reviews.llvm.org/D65182
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
