github-actions[bot] wrote:
<!--LLVM CODE FORMAT COMMENT: {clang-format}-->
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
<details>
<summary>
You can test this locally with the following command:
</summary>
``````````bash
git-clang-format --diff origin/main HEAD --extensions cpp --
lldb/unittests/Language/CPlusPlus/LibStdcppTupleTest.cpp
lldb/source/Plugins/Language/CPlusPlus/LibStdcppTuple.cpp
--diff_from_common_commit
``````````
:warning:
The reproduction instructions above might return results for more than one PR
in a stack if you are using a stacked PR workflow. You can limit the results by
changing `origin/main` to the base branch/commit you want to compare against.
:warning:
</details>
<details>
<summary>
View the diff from clang-format here.
</summary>
``````````diff
diff --git a/lldb/unittests/Language/CPlusPlus/LibStdcppTupleTest.cpp
b/lldb/unittests/Language/CPlusPlus/LibStdcppTupleTest.cpp
index e85592fb1..9c72796e0 100644
--- a/lldb/unittests/Language/CPlusPlus/LibStdcppTupleTest.cpp
+++ b/lldb/unittests/Language/CPlusPlus/LibStdcppTupleTest.cpp
@@ -113,9 +113,9 @@ public:
// Add the inner type as a field of the outer type
TypeSystemClang::StartTagDeclarationDefinition(outer_type);
- m_type_system->AddFieldToRecordType(
- outer_type, "std::_Tuple_impl<0, int>", inner_type,
- lldb::AccessType::eAccessPublic, 0);
+ m_type_system->AddFieldToRecordType(outer_type, "std::_Tuple_impl<0, int>",
+ inner_type,
+ lldb::AccessType::eAccessPublic, 0);
TypeSystemClang::CompleteTagDeclarationDefinition(outer_type);
return outer_type;
``````````
</details>
https://github.com/llvm/llvm-project/pull/175700
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
