summaryrefslogtreecommitdiffstats
path: root/llvm/lib
diff options
context:
space:
mode:
authorDaniel Jasper <djasper@google.com>2013-07-10 14:02:49 +0000
committerDaniel Jasper <djasper@google.com>2013-07-10 14:02:49 +0000
commitb10cbc45ad4ea8c75caef27b203c2f7044414b56 (patch)
tree7014ec85bafcbb901673147874fcd50b30c792b5 /llvm/lib
parent123fdb34133631b38ec9cb184f048da462511485 (diff)
downloadbcm5719-llvm-b10cbc45ad4ea8c75caef27b203c2f7044414b56.tar.gz
bcm5719-llvm-b10cbc45ad4ea8c75caef27b203c2f7044414b56.zip
Add experimental flag for adaptive parameter bin-packing.
This is not activated for any style, might change or go away completely. For those that want to play around with it, set ExperimentalAutoDetectBinPacking to true. clang-format will then: Look at whether function calls/declarations/definitions are currently formatted with one parameter per line (on a case-by-case basis). If so, clang-format will avoid bin-packing the parameters. If all parameters are on one line (thus that line is "inconclusive"), clang-format will make the choice dependent on whether there are other bin-packed calls/declarations in the same file. The reason for this change is that bin-packing in some situations can be really bad and an author might opt to put one parameter on each line. If the author does that, he might want clang-format not to mess with that. If the author is unhappy with the one-per-line formatting, clang-format can easily be convinced to bin-pack by putting any two parameters on the same line. llvm-svn: 186003
Diffstat (limited to 'llvm/lib')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud