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:
my_assert(false);
to mean abort in debug mode, take my chances in release mode.
--