Re: Upgrade to clang-format-3.8

> On Mar 18, 2016, at 10:22 AM, Michael Park wrote: > > Hi James, > > Someone would need to propose to auto-format everything with clang-format > and convince the community > that while clang-format will never be perfect, it generates a systematic, > sane and just as readable

RE: Upgrade to clang-format-3.8

> Subject: Re: Upgrade to clang-format-3.8 > From: jor...@gmail.com > Date: Fri, 18 Mar 2016 09:45:22 -0700 > To: dev@mesos.apache.org > > > > On Mar 17, 2016, at 10:41 AM, Yong Tang <yong.tang.git...@outlook.com> > > wrote: > > > >

Re: Upgrade to clang-format-3.8

> On Mar 17, 2016, at 10:41 AM, Yong Tang wrote: > > Hi All > > > This email is to announce that the default configuration and the recommended > version of the clang-format is being upgraded to 3.8 (from 3.5) in mesos. > > > In clang-format-3.8, the newly

Upgrade to clang-format-3.8

Hi All This email is to announce that the default configuration and the recommended version of the clang-format is being upgraded to 3.8 (from 3.5) in mesos. In clang-format-3.8, the newly introduced option "AlignAfterOpenBracket: AlwaysBreak" closes the largest gap between ClangFormat and

Re: Upgrade to clang-format-3.8

Hi James, Someone would need to propose to auto-format everything with clang-format and convince the community that while clang-format will never be perfect, it generates a systematic, sane and just as readable codebase. If we can reach consensus on that, we could add it as a commit hook and no

Re: Upgrade to clang-format-3.8

On Fri, Mar 18, 2016 at 10:19 AM, Yong Tang wrote: > Hi James > > My understanding is that there are two epic associated. One is the > clang-format integration that formatting whitespaces, multiple lines, etc. > Another is the clang-tidy integration that helps