diff options
author | XDeme <66138117+XDeme@users.noreply.github.com> | 2023-12-13 16:57:56 -0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-12-13 11:57:56 -0800 |
commit | 9512d6d2133a15a3e6272cbadd7fbb479011ccdb (patch) | |
tree | 36f6f86facdadfe69fcd5362f60090780518e514 /llvm/tools/llvm-cov/CodeCoverage.cpp | |
parent | ddd13b6e5df5dc8a56fe7fca9c7a458663cd4687 (diff) | |
download | llvm-9512d6d2133a15a3e6272cbadd7fbb479011ccdb.zip llvm-9512d6d2133a15a3e6272cbadd7fbb479011ccdb.tar.gz llvm-9512d6d2133a15a3e6272cbadd7fbb479011ccdb.tar.bz2 |
[clang-format] Fix parsing of `operator<() {}` (#75144)
Fixes #74876.
During the parsing of `operator<(Foo&) {}`, there was no handling for
the operator<, so it called `consumeToken()` again, causing the
`AnnotationParser::Scopes` to have one additional left brace each time
it tried to parse it, leaving it unbalanced.
Because of this, in the following code:
```cpp
class Foo {
void operator<(Foo&) {}
Foo& f;
};
```
The `&` in the reference member, was being interpreted as
`TT_BinaryOperator` instead of `TT_PointerOrReference`.
Diffstat (limited to 'llvm/tools/llvm-cov/CodeCoverage.cpp')
0 files changed, 0 insertions, 0 deletions