Re: Change copyObject() to use typeof_unqual
| От | Tom Lane |
|---|---|
| Тема | Re: Change copyObject() to use typeof_unqual |
| Дата | |
| Msg-id | 2191112.1773612810@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: Change copyObject() to use typeof_unqual ("Jelte Fennema-Nio" <postgres@jeltef.nl>) |
| Ответы |
Re: Change copyObject() to use typeof_unqual
|
| Список | pgsql-hackers |
"Jelte Fennema-Nio" <postgres@jeltef.nl> writes:
> If not, then I'm starting to think that actually checking support for
> this feature for CLANG is probably easier to understand (and less
> fragile) than combining all of these tricks together. Attached is a
> patch to do so.
+1 for concept, but don't you need to fix meson.build too?
>> And alternative is that
>> we decide that we don't want to support this combination, meaning that
>> we would effectively require that clang is approximately as-old-or-newer
>> than gcc.
> Given that Tom seems to have reproduced this on Fedora 40, it sounds
> like we should fix it.
Yeah. Given Fedora's development cycle, it is a certainty that they
shipped gcc and clang versions no more than a couple months different
in age. So even if we wanted to adopt the restriction Peter suggests,
there are not-very-old systems on which it fails.
regards, tom lane
В списке pgsql-hackers по дате отправления: