| From: | "Smith, Peter" <peters(at)fast(dot)au(dot)fujitsu(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: Proposal: Add more compile-time asserts to expose inconsistencies. |
| Date: | 2019-10-27 11:44:54 |
| Message-ID: | 201DD0641B056142AC8C6645EC1B5F62014B961D89@SYD1217 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Andres Freund <andres(at)anarazel(dot)de> Sent: Sunday, 27 October 2019 12:03 PM
>>Ideally, the implementation should end up calling _Static_assert()
>>somehow, so that we get the compiler's native error message.
OK. I can work on that.
>>We could do a configure check for whether _Static_assert() works at
>>file scope. I don't know what the support for that is, but it seems to
>>work in gcc and clang
> I think it should work everywhere that has static assert. So we should need a separate configure check.
Er, that's a typo right? I think you meant: "So we *shouldn't* need a separate configure check"
Kind Regards
---
Peter Smith
Fujitsu Australia
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-10-27 14:45:13 | Re: Proposal: Add more compile-time asserts to expose inconsistencies. |
| Previous Message | Dilip Kumar | 2019-10-27 07:21:56 | Re: [HACKERS] Block level parallel vacuum |