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/test/Parser/macro-braces-recovery.cpp clang/lib/Lex/Lexer.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/Lex/Lexer.cpp b/clang/lib/Lex/Lexer.cpp
index 989c4e0cb..e19f91987 100644
--- a/clang/lib/Lex/Lexer.cpp
+++ b/clang/lib/Lex/Lexer.cpp
@@ -929,7 +929,8 @@ bool Lexer::isAtEndOfMacroExpansion(SourceLocation loc,
// During error recovery, a zero-length synthetic token might be inserted
// past the end of the FileID, e.g. inserting ")" when a macro-arg
// containing a comma should be guarded by parentheses. In this case,
- // afterLoc reaches the `NextLocalOffset` boundary, any operations on
afterLoc will be invalid!
+ // afterLoc reaches the `NextLocalOffset` boundary, any operations on
+ // afterLoc will be invalid!
const SrcMgr::SLocEntry &Entry = SM.getSLocEntry(FID);
assert(Entry.isExpansion() && "Should be in an expansion");
expansionLoc = Entry.getExpansion().getExpansionLocEnd();
``````````
</details>
https://github.com/llvm/llvm-project/pull/191734
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
