Date: Thu, 4 Apr 2024 12:16:40 -0400
On Thu, Apr 4, 2024 at 12:03 PM Jens Maurer <jens.maurer_at_[hidden]> wrote:
> Then go forward with whatever you feel you want to do.
> Personally, I'd expect C++, when it's rebased on C, to say that
> "unreachable" is never a macro even after #include <stddef.h>,
> because it jeopardizes the spelling "std::unreachable()", which
> is the "natural" C++ spelling of the facility.
Thanks Jens! If this is the direction WG21 is likely to go, that gives
me the information I need. And the extra background (from you and
others) helps me navigate the broader situation.
~Aaron
> Then go forward with whatever you feel you want to do.
> Personally, I'd expect C++, when it's rebased on C, to say that
> "unreachable" is never a macro even after #include <stddef.h>,
> because it jeopardizes the spelling "std::unreachable()", which
> is the "natural" C++ spelling of the facility.
Thanks Jens! If this is the direction WG21 is likely to go, that gives
me the information I need. And the extra background (from you and
others) helps me navigate the broader situation.
~Aaron
Received on 2024-04-04 16:16:53