Re: Spelling change in LLVM 14 API
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-10-26T01:21:40Z
Lists: pgsql-hackers
Attachments
- 0001-Track-LLVM-14-API-changes-2021-10-25.patch (text/x-patch) patch 0001
On Tue, Oct 26, 2021 at 1:52 PM Andres Freund <andres@anarazel.de> wrote: > On 2021-10-26 13:39:53 +1300, Thomas Munro wrote: > > According to my crystal ball, seawasp will shortly break again[1][2] > > and the attached patch will fix it. > > That feels lot more convincing though. Based on past experience it's not hard > to believe that the compile-time impact of the include the use of std::string > forces into a lot of places is pretty significant... > > Could we make old case a wrapper around the new case that just passes on the > error as a const char *? That should be more maintainable long-term, because > there's only one copy of the body? Here's one like that. The previous message "Track LLVM 14 API changes" didn't seem too scalable so I added date and commit ID.
Commits
-
Track LLVM 14 API changes, up to 2022-01-30.
- 807fee1a39de 15.0 landed
-
Track LLVM 14 API changes.
- e6a760020210 15.0 landed