It sounds almost like "unreachable" is more of a debugging tool for you than a performance enhancer. Tell me, do you use sanitizers or some other compiler flag to force it to crash?
well, we're *supposed* to be doing it for codegen and also to mark cases where compiler thinks we could fall off the end of a non-void function. But in day to day practice it's a handy crasher.. Which is a micro version of the great contracts debate.
do you use sanitizers or some other compiler flag
oh, I see, in debug mode we have some extra instrumentation there. Never actually noticed until today
Whether that means Apress/Ivor Horton and Peter Van Weert are working on a "Beginning C++23" book I can't say, but it does look possible. After all C++23 isn't as major a change to C++ as C++20 is.
*I found out about the new branches by doing a git pull for the C++ example source code.
More money spent on a hobby that is expensive enough. *sigh*
Given how useful "Beginning C++20" was for this non-beginner "Beginning C++23" would be something to consider purchasing, after Visual Studio implements the C++23 core language and library features.
So far VS is about on par with the other compilers, though what is and isn't implemented varies between the compilers, with at this time two notable exceptions for implementation.
1. The optional extended floating-point types will not be added.
2. Relaxing the requirements for time_point<>::clock. Something GCC won't be doing as well.