Re: r290084 - clang-format: Allow "single column" list layout even if that violates the

2016-12-19 Thread Tobias Grosser via cfe-commits
On Mon, Dec 19, 2016, at 09:07 AM, Daniel Jasper wrote: > Yeah, I just saw that when fixing polly format. I'll take a look. You then probably also saw the second issue: -Type *Params[] = {PointerType::getUnqual(FunctionType::get( - Builder.getVoidTy(), Builder.getInt8

Re: r290084 - clang-format: Allow "single column" list layout even if that violates the

2016-12-19 Thread Daniel Jasper via cfe-commits
Yeah, I just saw that when fixing polly format. I'll take a look. On Mon, Dec 19, 2016 at 9:05 AM, Tobias Grosser wrote: > Hi Daniel, > > this commit introduce an unnecessary string split, which does not seem > to be an intended result of the formatting style change this commit > introduced: > >

Re: r290084 - clang-format: Allow "single column" list layout even if that violates the

2016-12-19 Thread Tobias Grosser via cfe-commits
Hi Daniel, this commit introduce an unnecessary string split, which does not seem to be an intended result of the formatting style change this commit introduced: BEFORE: #define SCOP_STAT(NAME, DESC) llvm::Statistic RejectStatistics[] = { SCOP_STAT(CFG, ""), SCOP_STAT(InvalidTerminator,

r290084 - clang-format: Allow "single column" list layout even if that violates the

2016-12-18 Thread Daniel Jasper via cfe-commits
Author: djasper Date: Mon Dec 19 01:26:11 2016 New Revision: 290084 URL: http://llvm.org/viewvc/llvm-project?rev=290084&view=rev Log: clang-format: Allow "single column" list layout even if that violates the column limit. Single-column layout basically means that we format the list with one eleme