2017-01-03 22:35:47 +08:00
|
|
|
//===--- Diagnostic.cpp - Framework for clang diagnostics tools ----------===//
|
|
|
|
//
|
2019-01-19 16:50:56 +08:00
|
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
2017-01-03 22:35:47 +08:00
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
//
|
|
|
|
// Implements classes to support/store diagnostics refactoring.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
|
|
|
#include "clang/Tooling/Core/Diagnostic.h"
|
2020-02-25 21:56:57 +08:00
|
|
|
#include "clang/Basic/SourceLocation.h"
|
2017-01-03 22:35:47 +08:00
|
|
|
#include "clang/Basic/SourceManager.h"
|
[clang-tidy] Add fix descriptions to clang-tidy checks.
Summary:
Motivation/Context: in the code review system integrating with clang-tidy,
clang-tidy doesn't provide a human-readable description of the fix. Usually
developers have to preview a code diff (before vs after apply the fix) to
understand what the fix does before applying a fix.
This patch proposes that each clang-tidy check provides a short and
actional fix description that can be shown in the UI, so that users can know
what the fix does without previewing diff.
This patch extends clang-tidy framework to support fix descriptions (will add implementations for
existing checks in the future). Fix descriptions and fixes are emitted via diagnostic::Note (rather than
attaching the main warning diagnostic).
Before this patch:
```
void MyCheck::check(...) {
...
diag(loc, "my check warning") << FixtItHint::CreateReplacement(...);
}
```
After:
```
void MyCheck::check(...) {
...
diag(loc, "my check warning"); // Emit a check warning
diag(loc, "fix description", DiagnosticIDs::Note) << FixtItHint::CreateReplacement(...); // Emit a diagnostic note and a fix
}
```
Reviewers: sammccall, alexfh
Reviewed By: alexfh
Subscribers: MyDeveloperDay, Eugene.Zelenko, aaron.ballman, JonasToth, xazax.hun, jdoerfert, cfe-commits
Tags: #clang-tools-extra, #clang
Differential Revision: https://reviews.llvm.org/D59932
llvm-svn: 358576
2019-04-17 20:53:59 +08:00
|
|
|
#include "llvm/ADT/STLExtras.h"
|
2017-01-03 22:35:47 +08:00
|
|
|
|
|
|
|
namespace clang {
|
|
|
|
namespace tooling {
|
|
|
|
|
|
|
|
DiagnosticMessage::DiagnosticMessage(llvm::StringRef Message)
|
|
|
|
: Message(Message), FileOffset(0) {}
|
|
|
|
|
|
|
|
DiagnosticMessage::DiagnosticMessage(llvm::StringRef Message,
|
|
|
|
const SourceManager &Sources,
|
|
|
|
SourceLocation Loc)
|
2018-11-21 09:08:46 +08:00
|
|
|
: Message(Message), FileOffset(0) {
|
2017-01-03 22:35:47 +08:00
|
|
|
assert(Loc.isValid() && Loc.isFileID());
|
2020-01-29 03:23:46 +08:00
|
|
|
FilePath = std::string(Sources.getFilename(Loc));
|
2018-11-21 09:08:46 +08:00
|
|
|
|
|
|
|
// Don't store offset in the scratch space. It doesn't tell anything to the
|
|
|
|
// user. Moreover, it depends on the history of macro expansions and thus
|
|
|
|
// prevents deduplication of warnings in headers.
|
|
|
|
if (!FilePath.empty())
|
|
|
|
FileOffset = Sources.getFileOffset(Loc);
|
2017-01-03 22:35:47 +08:00
|
|
|
}
|
|
|
|
|
2020-02-25 21:56:57 +08:00
|
|
|
FileByteRange::FileByteRange(
|
|
|
|
const SourceManager &Sources, CharSourceRange Range)
|
|
|
|
: FileOffset(0), Length(0) {
|
|
|
|
FilePath = std::string(Sources.getFilename(Range.getBegin()));
|
|
|
|
if (!FilePath.empty()) {
|
|
|
|
FileOffset = Sources.getFileOffset(Range.getBegin());
|
|
|
|
Length = Sources.getFileOffset(Range.getEnd()) - FileOffset;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2017-01-03 22:35:47 +08:00
|
|
|
Diagnostic::Diagnostic(llvm::StringRef DiagnosticName,
|
|
|
|
Diagnostic::Level DiagLevel, StringRef BuildDirectory)
|
|
|
|
: DiagnosticName(DiagnosticName), DiagLevel(DiagLevel),
|
|
|
|
BuildDirectory(BuildDirectory) {}
|
|
|
|
|
|
|
|
Diagnostic::Diagnostic(llvm::StringRef DiagnosticName,
|
2017-07-05 19:45:09 +08:00
|
|
|
const DiagnosticMessage &Message,
|
|
|
|
const SmallVector<DiagnosticMessage, 1> &Notes,
|
2020-02-25 21:56:57 +08:00
|
|
|
Level DiagLevel, llvm::StringRef BuildDirectory,
|
|
|
|
const SmallVector<FileByteRange, 1> &Ranges)
|
[clang-tidy] Add fix descriptions to clang-tidy checks.
Summary:
Motivation/Context: in the code review system integrating with clang-tidy,
clang-tidy doesn't provide a human-readable description of the fix. Usually
developers have to preview a code diff (before vs after apply the fix) to
understand what the fix does before applying a fix.
This patch proposes that each clang-tidy check provides a short and
actional fix description that can be shown in the UI, so that users can know
what the fix does without previewing diff.
This patch extends clang-tidy framework to support fix descriptions (will add implementations for
existing checks in the future). Fix descriptions and fixes are emitted via diagnostic::Note (rather than
attaching the main warning diagnostic).
Before this patch:
```
void MyCheck::check(...) {
...
diag(loc, "my check warning") << FixtItHint::CreateReplacement(...);
}
```
After:
```
void MyCheck::check(...) {
...
diag(loc, "my check warning"); // Emit a check warning
diag(loc, "fix description", DiagnosticIDs::Note) << FixtItHint::CreateReplacement(...); // Emit a diagnostic note and a fix
}
```
Reviewers: sammccall, alexfh
Reviewed By: alexfh
Subscribers: MyDeveloperDay, Eugene.Zelenko, aaron.ballman, JonasToth, xazax.hun, jdoerfert, cfe-commits
Tags: #clang-tools-extra, #clang
Differential Revision: https://reviews.llvm.org/D59932
llvm-svn: 358576
2019-04-17 20:53:59 +08:00
|
|
|
: DiagnosticName(DiagnosticName), Message(Message), Notes(Notes),
|
2020-02-25 21:56:57 +08:00
|
|
|
DiagLevel(DiagLevel), BuildDirectory(BuildDirectory), Ranges(Ranges) {}
|
2017-01-03 22:35:47 +08:00
|
|
|
|
[clang-tidy] Add fix descriptions to clang-tidy checks.
Summary:
Motivation/Context: in the code review system integrating with clang-tidy,
clang-tidy doesn't provide a human-readable description of the fix. Usually
developers have to preview a code diff (before vs after apply the fix) to
understand what the fix does before applying a fix.
This patch proposes that each clang-tidy check provides a short and
actional fix description that can be shown in the UI, so that users can know
what the fix does without previewing diff.
This patch extends clang-tidy framework to support fix descriptions (will add implementations for
existing checks in the future). Fix descriptions and fixes are emitted via diagnostic::Note (rather than
attaching the main warning diagnostic).
Before this patch:
```
void MyCheck::check(...) {
...
diag(loc, "my check warning") << FixtItHint::CreateReplacement(...);
}
```
After:
```
void MyCheck::check(...) {
...
diag(loc, "my check warning"); // Emit a check warning
diag(loc, "fix description", DiagnosticIDs::Note) << FixtItHint::CreateReplacement(...); // Emit a diagnostic note and a fix
}
```
Reviewers: sammccall, alexfh
Reviewed By: alexfh
Subscribers: MyDeveloperDay, Eugene.Zelenko, aaron.ballman, JonasToth, xazax.hun, jdoerfert, cfe-commits
Tags: #clang-tools-extra, #clang
Differential Revision: https://reviews.llvm.org/D59932
llvm-svn: 358576
2019-04-17 20:53:59 +08:00
|
|
|
const llvm::StringMap<Replacements> *selectFirstFix(const Diagnostic& D) {
|
|
|
|
if (!D.Message.Fix.empty())
|
|
|
|
return &D.Message.Fix;
|
|
|
|
auto Iter = llvm::find_if(D.Notes, [](const tooling::DiagnosticMessage &D) {
|
|
|
|
return !D.Fix.empty();
|
|
|
|
});
|
|
|
|
if (Iter != D.Notes.end())
|
|
|
|
return &Iter->Fix;
|
|
|
|
return nullptr;
|
|
|
|
}
|
|
|
|
|
2017-01-03 22:35:47 +08:00
|
|
|
} // end namespace tooling
|
|
|
|
} // end namespace clang
|