diff options
| author | mydeveloperday <mydeveloperday@gmail.com> | 2020-05-02 15:42:20 +0100 |
|---|---|---|
| committer | mydeveloperday <mydeveloperday@gmail.com> | 2020-05-02 15:42:20 +0100 |
| commit | ece7e95f02cdcdf9fa7c6fdfbf6db92e4cc0c87e (patch) | |
| tree | 99b891499f27caa1b10fdffb94e3e5f637c4ce15 /clang/unittests/Format/FormatTestCSharp.cpp | |
| parent | d3bc86c2ed579c3b854d37c114a85901ed8cfb9a (diff) | |
| download | llvm-ece7e95f02cdcdf9fa7c6fdfbf6db92e4cc0c87e.zip llvm-ece7e95f02cdcdf9fa7c6fdfbf6db92e4cc0c87e.tar.gz llvm-ece7e95f02cdcdf9fa7c6fdfbf6db92e4cc0c87e.tar.bz2 | |
[clang-format] NFC - clang-format the FormatTests
Summary:
Ensure the clang-format unit tests are themselves clang-formatted
Having areas of the llvm code which are clang-format clean, give us more areas to run new clang-format binaries on ensuring we haven't broken anything.
It seems to me we SHOULD have this clang-formatted at a minimum, otherwise how can we expect others to use clang-format if we "don't eat our own dogfood", also if the tests are dependent on the formatting of the code then that would also be bad!
Reviewed By: sammccall
Subscribers: cfe-commits
Tags: #clang, #clang-format
Differential Revision: https://reviews.llvm.org/D79204
Diffstat (limited to 'clang/unittests/Format/FormatTestCSharp.cpp')
| -rw-r--r-- | clang/unittests/Format/FormatTestCSharp.cpp | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/clang/unittests/Format/FormatTestCSharp.cpp b/clang/unittests/Format/FormatTestCSharp.cpp index 4036790..d8d992e 100644 --- a/clang/unittests/Format/FormatTestCSharp.cpp +++ b/clang/unittests/Format/FormatTestCSharp.cpp @@ -761,7 +761,8 @@ TEST_F(FormatTestCSharp, CSharpGenericTypeConstraints) { verifyFormat(R"(// class ItemFactory<T> - where T : new() {})", Style); + where T : new() {})", + Style); verifyFormat(R"(// class Dictionary<TKey, TVal> |