Subject: Re: Missing non-void return on some paths
From: JF Bastien (cxx_at_[hidden])
Date: 2021-05-08 14:04:05
On Sat, May 8, 2021 at 11:52 AM Nevin Liber via SG12 <sg12_at_[hidden]>
> On Thu, May 6, 2021 at 6:47 PM JF Bastien via SG12 <sg12_at_[hidden]>
>> Compilers diagnose when functions can't be proved to return, and I
>> wouldn't work on a codebase without this diagnostic enabled as an error. Is
>> there a valid reason to keep this UB around?
> How does one write an assert-type macro which, when it is disabled, still
> prevents this type of warning/error? Because people do write:
> to mean abort in debug mode, take my chances in release mode.
I donât think I understand what youâre asking... but it sounds like
#define YOLO() abort()
#define YOLO() std::unreachable() // or __builtin_unreachable()
But I donât know what youâre going for, and whether this is what youâre
SG12 list run by email@example.com