diff options
| author | Vladimir Plyashkun <vladimir.plyashkun@jetbrains.com> | 2022-08-17 19:25:48 +0100 |
|---|---|---|
| committer | Nathan James <n.james93@hotmail.co.uk> | 2022-08-17 19:25:59 +0100 |
| commit | fa8f8616028abbc10aa5a3ad4641e8a40ec20cc8 (patch) | |
| tree | 5997484ab94e2d9f45123af47c4b11ce38eac10c /lldb/source/Commands/CommandObjectThread.cpp | |
| parent | a5b11f40f8da824435d43d2332ac8870c1386868 (diff) | |
| download | llvm-fa8f8616028abbc10aa5a3ad4641e8a40ec20cc8.zip llvm-fa8f8616028abbc10aa5a3ad4641e8a40ec20cc8.tar.gz llvm-fa8f8616028abbc10aa5a3ad4641e8a40ec20cc8.tar.bz2 | |
[clang-tidy] hicpp-signed-bitwise - Return location of the operand (and not of the operator beginning)
Currently, the "hicpp/signed-bitwise" check returns the beginning of the binary/unary operator as location, which sometimes confuses users in the IDE due to incorrect [[ https://youtrack.jetbrains.com/issue/CPP-12445/Clang-Tidy-highlighting-for-binary-operators-applied-to-wrong-operand | highlighting ]].
Yes, the offset from Ranges can be used for this particular check, but i suppose better solution is to return begin location of the problematic operand instead of operator.
Reviewed By: njames93
Differential Revision: https://reviews.llvm.org/D131678
Diffstat (limited to 'lldb/source/Commands/CommandObjectThread.cpp')
0 files changed, 0 insertions, 0 deletions