Fix clang format #4585
Merged
Fix clang format #4585
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Feb 12, 2025
rscampos
reviewed
Feb 14, 2025
geyslan
force-pushed
the
fix-clang-format
branch
from
c3a7017 to
24132c6
Compare
PenaltyReturnTypeOnItsOwnLine was duplicated in the .clang-format file. It was crashing the clangd server. Since the value of PenaltyReturnTypeOnItsOwnLine was being wrongly interpreted, this opportunistically changes the other Penalty* values.
geyslan
force-pushed
the
fix-clang-format
branch
from
24132c6 to
93a443d
Compare
geyslan
force-pushed
the
fix-clang-format
branch
from
93a443d to
12a7e77
Compare
|
/fast-forward |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1. Explain what the PR does
12a7e77 chore(ebpf): format apply based on the latest fix
d3fc3e1 fix: remove duplicate entry in .clang-format
d3fc3e1 fix: remove duplicate entry in .clang-format
2. Explain how to test it
3. Other comments