For clauses without parentheses it was annotated as TT_InheritanceColon.
Relates to https://github.com/llvm/llvm-project/issues/56215
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
clang/unittests/Format/TokenAnnotatorTest.cpp | ||
---|---|---|
823–836 | Can you make it a function or lambda? |
clang/unittests/Format/TokenAnnotatorTest.cpp | ||
---|---|---|
823–836 | Often thought about that. But as @MyDeveloperDay mentioned in different other reviews, we would loose the line where the EXPECT failed, since it would always be the same line. One step to mitigate that would be to return a bool, then one would loose the "subexpect", only knows which subtest failed. But an idea I have right now would be to add a StringRef parameter which is then fed into the expect/assert to identify the subtest. |
clang/unittests/Format/TokenAnnotatorTest.cpp | ||
---|---|---|
823–836 | You can then add a function taking a source location maybe (+ optionally a macro passing __FILE__ and __LINE__). WDYT? |
clang/unittests/Format/TokenAnnotatorTest.cpp | ||
---|---|---|
823–836 | Let's take care of this in a separate patch then. If a function or lambda won't do, we can at least use a macro instead? |
Can you make it a function or lambda?