Re: Synchronize with imath upstream
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@lists.postgresql.org,
Alvaro Herrera <alvherre@2ndquadrant.com>,
David Fetter <david@fetter.org>,
Andrew Gierth <andrew@tao11.riddles.org.uk>,
Noah Misch <noah@leadboat.com>, pgsql-hackers@postgresql.org
Date: 2019-02-06T15:15:24Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > On February 6, 2019 5:17:50 AM GMT+05:30, Alvaro Herrera <alvherre@2ndquadrant.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
Commits
-
Import changes from IMath versions (1.3, 1.29].
- 48e24ba6b7fd 12.0 landed
-
Cherry-pick security-relevant fixes from upstream imath library.
- 8b59672d8d23 9.5.0 cited