Re: Make copyObject work in C++

Jelte Fennema <postgres@jeltef.nl>

From: "Jelte Fennema-Nio" <postgres@jeltef.nl>
To: "Peter Eisentraut" <peter@eisentraut.org>, "PostgreSQL Hackers" <pgsql-hackers@lists.postgresql.org>, "Thomas Munro" <thomas.munro@gmail.com>
Date: 2026-01-03T09:32:28Z
Lists: pgsql-hackers

Attachments

On Tue Dec 16, 2025 at 1:28 PM CET, Peter Eisentraut wrote:
> I think it might be good to create a test extension written in C++, like 
> under src/test/modules/, and sprinkle it with various constructs like 
> copyObject() and static assertions, and whatever else we find that is 
> possibly problematic.

Attached is a patchset that does that. It required a few more fixes to
make the extension compile on MSVC too.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Enable test_cplusplusext with MSVC

  2. Disable some C++ warnings in MSVC

  3. meson: Make room for C++-only warning flags for MSVC

  4. Make fixed-length list building macros work in C++

  5. Make unconstify and unvolatize use StaticAssertVariableIsOfTypeMacro

  6. Use typeof everywhere instead of compiler specific spellings

  7. Test List macros in C++ extensions

  8. Test most StaticAssert macros in C++ extensions

  9. Revert "Change copyObject() to use typeof_unqual"

  10. Fix for C++ compatibility

  11. tests: Add a test C++ extension module