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 b653357141030620ce3e70ea939efbcb71d40657 
bcd8c81c5fbc249886c53d8a2d1bc21a3f9e1ffd -- 
lldb/include/lldb/API/SBCommandInterpreterRunOptions.h 
lldb/include/lldb/Interpreter/CommandInterpreter.h 
lldb/source/API/SBCommandInterpreterRunOptions.cpp 
lldb/source/Interpreter/CommandInterpreter.cpp
``````````

</details>

<details>
<summary>
View the diff from clang-format here.
</summary>

``````````diff
diff --git a/lldb/include/lldb/API/SBCommandInterpreterRunOptions.h 
b/lldb/include/lldb/API/SBCommandInterpreterRunOptions.h
index b32a8ca51c..c11bf5e404 100644
--- a/lldb/include/lldb/API/SBCommandInterpreterRunOptions.h
+++ b/lldb/include/lldb/API/SBCommandInterpreterRunOptions.h
@@ -71,14 +71,14 @@ public:
   bool GetSpawnThread() const;
 
   void SetSpawnThread(bool);
-  
+
   bool GetAllowRepeats() const;
-  
+
   // By default, RunCommandInterpreter will discard repeats if the
   // IOHandler being used is not interactive.  Setting AllowRepeats to true
   // will override this behavior and always process empty lines in the input
   // as a repeat command.
-  void  SetAllowRepeats(bool);
+  void SetAllowRepeats(bool);
 
 private:
   lldb_private::CommandInterpreterRunOptions *get() const;
diff --git a/lldb/include/lldb/Interpreter/CommandInterpreter.h 
b/lldb/include/lldb/Interpreter/CommandInterpreter.h
index 5c2bcd9968..665336fbf8 100644
--- a/lldb/include/lldb/Interpreter/CommandInterpreter.h
+++ b/lldb/include/lldb/Interpreter/CommandInterpreter.h
@@ -100,7 +100,8 @@ public:
                                LazyBool stop_on_error, LazyBool stop_on_crash,
                                LazyBool echo_commands, LazyBool echo_comments,
                                LazyBool print_results, LazyBool print_errors,
-                               LazyBool add_to_history, LazyBool 
process_repeats)
+                               LazyBool add_to_history,
+                               LazyBool process_repeats)
       : m_stop_on_continue(stop_on_continue), m_stop_on_error(stop_on_error),
         m_stop_on_crash(stop_on_crash), m_echo_commands(echo_commands),
         m_echo_comment_commands(echo_comments), m_print_results(print_results),
diff --git a/lldb/source/Interpreter/CommandInterpreter.cpp 
b/lldb/source/Interpreter/CommandInterpreter.cpp
index 95b9bb491a..d82662fae9 100644
--- a/lldb/source/Interpreter/CommandInterpreter.cpp
+++ b/lldb/source/Interpreter/CommandInterpreter.cpp
@@ -2708,7 +2708,7 @@ enum {
   eHandleCommandFlagPrintResult = (1u << 4),
   eHandleCommandFlagPrintErrors = (1u << 5),
   eHandleCommandFlagStopOnCrash = (1u << 6),
-  eHandleCommandFlagAllowRepeats  = (1u << 7)
+  eHandleCommandFlagAllowRepeats = (1u << 7)
 };
 
 void CommandInterpreter::HandleCommandsFromFile(
@@ -3130,8 +3130,9 @@ void CommandInterpreter::IOHandlerInputComplete(IOHandler 
&io_handler,
       return;
 
   const bool is_interactive = io_handler.GetIsInteractive();
-  bool allow_repeats = 
io_handler.GetFlags().Test(eHandleCommandFlagAllowRepeats);
-  
+  bool allow_repeats =
+      io_handler.GetFlags().Test(eHandleCommandFlagAllowRepeats);
+
   if (!is_interactive && !allow_repeats) {
     // When we are not interactive, don't execute blank lines. This will happen
     // sourcing a commands file. We don't want blank lines to repeat the

``````````

</details>


https://github.com/llvm/llvm-project/pull/94786
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to