[clang-tidy] Don't emit the same fixit multiple times.

If we had many header files we would attach the fix-it for all files to all
warnings, oops. This is harmless 99.9% of the time but can confuse the rewriter
in some edge cases. Sadly I failed to create a small test case for this.

While there move fix-its instead of copying.

llvm-svn: 217951

1 files changed, 5 insertions, 5 deletions

diff --git a/clang-tools-extra/clang-tidy/utils/HeaderGuard.cpp b/clang-tools-extra/clang-tidy/utils/HeaderGuard.cpp
index cf187c25a27..d18cf1603ed 100644
--- a/clang-tools-extra/clang-tidy/utils/HeaderGuard.cpp
+++ b/clang-tools-extra/clang-tidy/utils/HeaderGuard.cpp
@@ -125,15 +125,16 @@ public:
         if (CurHeaderGuard != NewGuard) {
           auto D = Check->diag(Ifndef,
                                "header guard does not follow preferred style");
-          for (const FixItHint Fix : FixIts)
-            D.AddFixItHint(Fix);
+          for (FixItHint &Fix : FixIts)
+            D.AddFixItHint(std::move(Fix));
         } else {
           auto D = Check->diag(EndIf, "#endif for a header guard should "
                                       "reference the guard macro in a comment");
-          for (const FixItHint Fix : FixIts)
-            D.AddFixItHint(Fix);
+          for (FixItHint &Fix : FixIts)
+            D.AddFixItHint(std::move(Fix));
         }
       }
+      FixIts.clear();
     }
 
     // Emit warnings for headers that are missing guards.
@@ -144,7 +145,6 @@ public:
     Files.clear();
     Ifndefs.clear();
     EndIfs.clear();
-    FixIts.clear();
   }
 
   bool wouldFixEndifComment(StringRef FileName, SourceLocation EndIf,