Jonathan Wakely

I forgot to link to the changes already approved for C++23: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p1642r11.html

OK, thanks for the reply. FWIW when we implement Ben's proposals in libstdc++ I don't plan to make it conditional on using C++23 mode. A freestanding implementation is allowed to...

It's happening in frequently rebased git branches for now, but might be finished in the next few days and will get committed upstream. You can find me on GCC's developer...

> It's happening in frequently rebased git branches for now, but might be finished in the next few days and will get committed upstream. That work is now upstream :tada:

I see loads of -Werror=maybe-uninitialized errors when building master on Fedora 38 (boost 1.78.0, gcc 13.0.1). I added -Wno-error=maybe-uninitialized to downgrade them to warnings while I was looking into something...

There's also http://mysqlcppapi.sourceforge.net/ but it's moribund (in theory I maintain it but I haven't touched it in years and recommend MySQL++ instead).

> ES.79 is a terrible advice that will cause unreliably code and serious bugs once project evolve and new enum values get added. Adding a default case to switch statements...

Imagine there's another non-default case that doesn't return. In any case, `default` isn't going to be removed from the language, so that part of your issue is just silly. Regarding...

You've shown why you don't want to use `default` in your code. Fine. So don't use it. That's allowed by ES.79. It doesn't try to stop you banning `default` in...

> > You failed to answer my question: what part of the guideline says you have to use `default`? > > In the **Enforcement** section: `Flag switch-statements over an enumeration...