Make clang-format cleaner remove redundant commas/colons in constructor initializer list.
Details
- Reviewers
klimek djasper - Commits
- rGce5e4bc7ac87: Make clang-format cleaner remove redundant commas in list and redundant colon…
rC269888: Make clang-format cleaner remove redundant commas in list and redundant colon…
rL269888: Make clang-format cleaner remove redundant commas in list and redundant colon…
Diff Detail
- Repository
- rL LLVM
Event Timeline
lib/Format/Format.cpp | ||
---|---|---|
1821 ↗ | (On Diff #55810) | Why are we restricting this to constructor initializers? I think we should directly be more generic and clean up different lists. Also, as an idea? Could we make this very generic and implement a function that analyzes a line for a specific sequence of tokens? E.g., I would assume that then the current checkConstructorInitList() could be written as: cleanupLeft(tok::comma, tok::comma); cleanupLeft(tok::comma, tok::l_brace); cleanupRight(tok::colon, tok::comma); cleanupLeft(tok::colon, tok::l_brace); With cleanupLeft/Right meaning: Find this sequence of tokens (ignoring comments) and then clean up the left or the right side. Not sure about the exact names of functions etc. What do you think? |
lib/Format/Format.cpp | ||
---|---|---|
1821 ↗ | (On Diff #55810) | I think having a generic cleanupLeft(tok::comma, tok::comma) is a great idea; however, the other three functions seem a little too generic since they'd probably only be used in constructor initializers? E.g. an expression like condition ? something : { list } would be a false positive for cleanupLeft(tok::colon, tok::l_brace), and [{...}, {...}] might be a false positive for cleanupLeft(tok::comma, tok::l_brace). Also, it seems to me that cleanupRight(tok::colon, tok::comma) would only happen in constructor initializers? I think a mixed solution might work as well. For example, we can run cleanupLeft(tok::comma, tok::comma) across all tokens in the code, and then for constructor initializers specifically, we handle redundant colon and trailing comma. What do you think? As for comments, we can probably handle them after all cleanup is done. |
- Extended redundant comma cleanup to general lists, and change the way constructor initializer list is handled. Removed comments cleanup, leave it for a future patch.
I experimented a bit. What do you think of this?
lib/Format/Format.cpp | ||
---|---|---|
1822 ↗ | (On Diff #56696) | You could turn this into: for (auto &Line : AnnotatedLines) { if (Line->Affected) { cleanupRight(Line->First, tok::comma, tok::comma); cleanupRight(Line->First, TT_CtorInitializerColon, tok::comma); cleanupLeft(Line->First, tok::comma, tok::l_brace); cleanupLeft(Line->First, TT_CtorInitializerColon, tok::l_brace); } } |
1914 ↗ | (On Diff #56696) | And all of this into: // Checks pairs {start, start->next},..., {end->previous, end} and deletes one // of the token in the pair if the left token has \p LK token kind and the // right token has \p RK token kind. If \p DeleteLeft is true, the left token // is deleted on match; otherwise, the right token is deleted. template <typename LeftKind, typename RightKind> void cleanupPair(FormatToken *Start, LeftKind LK, RightKind RK, bool DeleteLeft) { auto NextNotDeleted = [this](const FormatToken &Tok) -> FormatToken * { for (auto *Res = Tok.Next; Res; Res = Res->Next) if (!Res->is(tok::comment) && DeletedTokens.find(Res) == DeletedTokens.end()) return Res; return nullptr; }; for (auto *Left = Start; Left;) { auto *Right = NextNotDeleted(*Left); if (!Right) break; if (Left->is(LK) && Right->is(RK)) { deleteToken(DeleteLeft ? Left : Right); // If the right token is deleted, we should keep the left token // unchanged and pair it with the new right token. if (!DeleteLeft) continue; } Left = Right; } } template <typename LeftKind, typename RightKind> void cleanupLeft(FormatToken *Start, LeftKind LK, RightKind RK) { cleanupPair(Start, LK, RK, /*DeleteLeft=*/true); } template <typename LeftKind, typename RightKind> void cleanupRight(FormatToken *Start, LeftKind LK, RightKind RK) { cleanupPair(Start, LK, RK, /*DeleteLeft=*/false); } |
lib/Format/Format.cpp | ||
---|---|---|
1822 ↗ | (On Diff #56696) | Wouldn't cleanupLeft(Line->First, tok::comma, tok::l_brace); also remove the comma from std::vector<std::vector<int>> = {{...}, {...}}? |
lib/Format/Format.cpp | ||
---|---|---|
1822 ↗ | (On Diff #56696) | I should've added this case into unit test, sorry... But I think we can either handle constructor initializer's tok::l_brace specially or annotate it? The later solution can enable us to do cleanupLeft(Line->First, tok::comma, TT_CtorInitializerLBrace);. |
- Use reviewer's awesome templates for checkPair().
- Remove checkConstructorInitList().
- Moved InCtorInitializer context setting before checking tok::comma so that InCtorInitializer context can be set even we have syntax error ":," around ctor colon.
lib/Format/Format.cpp | ||
---|---|---|
1822 ↗ | (On Diff #56696) | Just found out constructor initializer's commas are already annotated. Then, this can be easily fixed with cleanupLeft(Line->First, TT_CtorInitializerComma, tok::l_brace);. |
1914 ↗ | (On Diff #56696) | Thanks for the awesome templates! |