Re: Synchronize with imath upstream

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, David Fetter <david(at)fetter(dot)org>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Synchronize with imath upstream
Date: 2019-02-06 15:15:24
Message-ID: 23413.1549466124@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On February 6, 2019 5:17:50 AM GMT+05:30, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>> I'm -1 for this myself. I think there are a few places that could
>> benefit from it, but my fear is that many *more* places would get
>> worse.

> Because of imported code like ryu and imath? And because it can make code considerably better when used judiciously.

I don't object to keeping imported code in a form that matches upstream
as best we can. (Should we also exclude such files from pgindent'ing?)

But changing conventions for our own code is an entirely different matter.
In this case, I think that having some places use it while the bulk of
the code doesn't is just a bad idea from a stylistic-consistency
standpoint. It's pretty much the same reason why we still aren't allowing
// comments --- there's no toolchain-based reason not to, but a mishmash of
comment styles would be ugly and hard to read.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Timmer, Marius 2019-02-06 15:19:56 Re: [PATCH] pg_hba.conf : new auth option : clientcert=verify-full
Previous Message Tom Lane 2019-02-06 15:09:22 Re: bug tracking system