Date: Wed, 05 Jul 2023 21:12:31 -0700
On Wednesday, 5 July 2023 19:41:46 PDT trtaab trtaab via Std-Proposals wrote:
> The term "silent" in the context of the proposal refers to the absence of
> additional output from the standard library, such as error messages or
> debug information. While crashes are not inherently silent, the use of a
> reliable crash mechanism, whether it's __builtin_trap() or other similar
> methods, is intended to provide a controlled program termination without
> generating extraneous output. The primary focus is on achieving a clean
> crash without introducing additional noise or debug information.
You probably need to standardise __builtin_trap() first, by making it a
function in the std namespace that others could use too.
It's too bad that C requires assert to be a macro, otherwise I'd suggest you
call it std::assert. I'm sure you can find a suitable name.
> The term "silent" in the context of the proposal refers to the absence of
> additional output from the standard library, such as error messages or
> debug information. While crashes are not inherently silent, the use of a
> reliable crash mechanism, whether it's __builtin_trap() or other similar
> methods, is intended to provide a controlled program termination without
> generating extraneous output. The primary focus is on achieving a clean
> crash without introducing additional noise or debug information.
You probably need to standardise __builtin_trap() first, by making it a
function in the std namespace that others could use too.
It's too bad that C requires assert to be a macro, otherwise I'd suggest you
call it std::assert. I'm sure you can find a suitable name.
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel DCAI Cloud Engineering
Received on 2023-07-06 04:12:33