summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/breakpoint
diff options
context:
space:
mode:
authorPaul Hoad <mydeveloperday@gmail.com>2019-10-04 14:16:59 +0000
committerPaul Hoad <mydeveloperday@gmail.com>2019-10-04 14:16:59 +0000
commitba12cec21f55cae6aaae0b57d08cab0de9358d51 (patch)
treede2195aa365975198c19ea6e3aef899089a1eb77 /lldb/packages/Python/lldbsuite/test/python_api/breakpoint
parentf44ca7f6eba468e146b0096a91dd9931b556aa86 (diff)
downloadbcm5719-llvm-ba12cec21f55cae6aaae0b57d08cab0de9358d51.tar.gz
bcm5719-llvm-ba12cec21f55cae6aaae0b57d08cab0de9358d51.zip
[clang-format] [PR43531] clang-format damages "alternative representations" for operators
Summary: https://bugs.llvm.org/show_bug.cgi?id=43531 Fix for clang-format incorrectly handles "alternative operators" as described by https://en.cppreference.com/w/cpp/language/operator_alternative compl = ~ not = ! these are unary operators, and clang-format will remove the space between them and a numeric constant this incorrectly formats the following code ``` int a compl 5; int a not 5; ``` into: ``` int a compl5; int a not5; ``` The code adds FIXME unit tests for "alternative token" representations for {} [] and # as defined by the same link, which would require a more detailed change to the FormatTokenLexer Reviewers: klimek, reuk, owenpan, mitchell-stellar, STL_MSFT Reviewed By: mitchell-stellar Subscribers: cfe-commits Tags: #clang-format, #clang-tools-extra, #clang Differential Revision: https://reviews.llvm.org/D68332 llvm-svn: 373750
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/breakpoint')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud