aboutsummaryrefslogtreecommitdiff
path: root/llvm/tools/llvm-readobj/llvm-readobj.cpp
diff options
context:
space:
mode:
authorDaniel Jasper <djasper@google.com>2015-08-21 11:44:57 +0000
committerDaniel Jasper <djasper@google.com>2015-08-21 11:44:57 +0000
commit100ffc632aa1f9d21ffe2cb66dba6afb59b579f6 (patch)
tree21720983f6ab9cd1145e8a97767b7d89becd2f37 /llvm/tools/llvm-readobj/llvm-readobj.cpp
parentd386a6ccb9c094087f982ffbdcd1d8880a4a462b (diff)
downloadllvm-100ffc632aa1f9d21ffe2cb66dba6afb59b579f6.zip
llvm-100ffc632aa1f9d21ffe2cb66dba6afb59b579f6.tar.gz
llvm-100ffc632aa1f9d21ffe2cb66dba6afb59b579f6.tar.bz2
clang-format: Be more conservative about specially indenting blocks in C++.
This is a bit of a step back of what we did in r222531, as there are some corner cases in C++, where this kind of formatting is really bad. Example: Before: virtual aaaaaaaaaaaaaaaa(std::function<bool()> IsKindWeWant = [&]() { return true; }, aaaaa aaaaaaaaa); After: virtual aaaaaaaaaaaaaaaa(std::function<bool()> IsKindWeWant = [&]() { return true; }, aaaaa aaaaaaaaa); The block formatting logic in JavaScript will probably go some other changes, too, and we'll potentially be able to make the rules more consistent again. For now, this seems to be the best approach for C++. llvm-svn: 245694
Diffstat (limited to 'llvm/tools/llvm-readobj/llvm-readobj.cpp')
0 files changed, 0 insertions, 0 deletions