From: Andres Freund <andres@anarazel.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