On Mon, 26 Feb 2024, David Laight <David.Laight@xxxxxxxxxx> wrote: > From: Jani Nikula >> Sent: 26 February 2024 09:28 >> >> On Sun, 25 Feb 2024, David Laight <David.Laight@xxxxxxxxxx> wrote: >> > The wrapper just adds two more lines of error output when the test fails. >> >> There are only a handful of places in kernel code that use >> _Static_assert() directly. Nearly 900 instances of static_assert(). > > How many of those supply an error message? At a glance, not many. >> Are we now saying it's fine to use _Static_assert() directly all over >> the place? People will copy-paste and cargo cult. > > Is that actually a problem? I don't know. I'm asking. Usually when we have compiler wrappers, they're meant to be used instead of the thing being wrapped. This series deviates from that, so it would seem to fair to mention it slightly more verbosely than just stating what's being done. > The wrapper allows the error message to be omitted and substitutes > the text of the conditional. > But it isn't 'free'. > As well as slightly slowing down the compilation, the error messages > from the compiler get more difficult to interpret. > > Most of the static_assert() will probably never generate an error. > But the ones in min()/max() will so it is best to make them as > readable as possible. > (Don't even look as the mess clang makes....) I'm not arguing any of this. :) BR, Jani. -- Jani Nikula, Intel
