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 -- 
clang/lib/Analysis/LifetimeSafety/FactsGenerator.cpp 
clang/test/Sema/LifetimeSafety/safety.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/clang/lib/Analysis/LifetimeSafety/FactsGenerator.cpp 
b/clang/lib/Analysis/LifetimeSafety/FactsGenerator.cpp
index 65ec736c6..2ca6484d5 100644
--- a/clang/lib/Analysis/LifetimeSafety/FactsGenerator.cpp
+++ b/clang/lib/Analysis/LifetimeSafety/FactsGenerator.cpp
@@ -470,8 +470,8 @@ void FactsGenerator::handlePointerArithmetic(const 
BinaryOperator *BO) {
 void FactsGenerator::VisitBinaryOperator(const BinaryOperator *BO) {
   if (BO->getOpcode() == BO_PtrMemD || BO->getOpcode() == BO_PtrMemI) {
     // `obj.*pm` / `objptr->*pm` names a member of the object, so a borrow of 
it
-    // borrows the object; flow the object's origin into the result. For `.*` 
the
-    // object is the LHS; for `->*` it is the LHS pointer's pointee.
+    // borrows the object; flow the object's origin into the result. For `.*`
+    // the object is the LHS; for `->*` it is the LHS pointer's pointee.
     OriginList *Dst = getOriginsList(*BO);
     OriginList *ObjSrc =
         BO->getOpcode() == BO_PtrMemD

``````````

</details>


https://github.com/llvm/llvm-project/pull/204612
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to