Re: Automatic changes during the dev workflow [was: Re: Upcoming changes to our C++ Coding Style]

2018-12-17 Thread Ehsan Akhgari
On Mon, Dec 17, 2018 at 1:22 PM Steve Fink wrote: > In theory, I would definitely prefer if all the code were auto-formatted > during regular development(*), but in practice the performance means > it's not as transparent as it needs to be -- I have noticed that since > enabling the format-source

Re: Automatic changes during the dev workflow [was: Re: Upcoming changes to our C++ Coding Style]

2018-12-17 Thread Ehsan Akhgari
On Fri, Dec 14, 2018 at 4:55 PM Kartikaya Gupta wrote: > On Fri, Dec 14, 2018 at 1:58 PM Sylvestre Ledru > wrote: > > We have more and more tools at review phase (clang-format, flake8, > eslint, clang-tidy, codespell, etc) which propose some auto-fixes. > > Honestly I find it quite annoying when

Re: Automatic changes during the dev workflow [was: Re: Upcoming changes to our C++ Coding Style]

2018-12-17 Thread Steve Fink
In theory, I would definitely prefer if all the code were auto-formatted during regular development(*), but in practice the performance means it's not as transparent as it needs to be -- I have noticed that since enabling the format-source extension, rebasing my patch stacks is significantly sl

Re: Automatic changes during the dev workflow [was: Re: Upcoming changes to our C++ Coding Style]

2018-12-17 Thread Sylvestre Ledru
Le 14/12/2018 à 22:55, Kartikaya Gupta a écrit : On Fri, Dec 14, 2018 at 1:58 PM Sylvestre Ledru wrote: We have more and more tools at review phase (clang-format, flake8, eslint, clang-tidy, codespell, etc) which propose some auto-fixes. Honestly I find it quite annoying when I'm trying to r

Re: Automatic changes during the dev workflow [was: Re: Upcoming changes to our C++ Coding Style]

2018-12-16 Thread Jean-Yves Avenard
Hi > On 14 Dec 2018, at 7:57 pm, Sylvestre Ledru wrote: > > I think we should aim at option b) (updated automatically by bots after > submission to Phabricator) > > I don’t particularly fancy this idea. Finding yourself with different code on Phabricator and locally is a good way to shoot y

Automatic changes during the dev workflow [was: Re: Upcoming changes to our C++ Coding Style]

2018-12-15 Thread Sylvestre Ledru
I think we should aim at option b) (updated automatically by bots after submission to Phabricator) We have more and more tools at review phase (clang-format, flake8, eslint, clang-tidy, codespell, etc) which propose some auto-fixes. Currently, the turn around time of the tools is 14m on avera

Re: Automatic changes during the dev workflow [was: Re: Upcoming changes to our C++ Coding Style]

2018-12-15 Thread Kartikaya Gupta
On Fri, Dec 14, 2018 at 1:58 PM Sylvestre Ledru wrote: > We have more and more tools at review phase (clang-format, flake8, eslint, > clang-tidy, codespell, etc) which propose some auto-fixes. Honestly I find it quite annoying when I'm trying to review a patch and the phabricator diff is filled