Inspired by a comment in this r/cpp thread on how, well, hidden friends don't seem to be reflectable; this in the context of C++26 reflection.

Following up on the discussion from earlier this month among GCC developers over switching to C++20 by default for the GCC compiler as the default C++ standard when not otherwise set, that change has indeed happened. Merged now is the change defaulting to C++20 (well, the GNU++20 dialect) rather than C++17/GNU++17 when not otherwise specified when compiling C++ code.

GCC developers had discovered that their own codebase wasn't entire C++20 ready but they have been landing those fixes too this week so GCC 16 can jive happy with a C++20 default.

Following the recent idea floated to consider C++20 as the default C++ language dialect by the GCC compiler rather than C++17, it was discovered that the GNU Compiler Collection itself has problems building in C++20 model.

Compared to the default C++17 (GNU++17) dialect currently used by the GCC compiler, when trying to compile GCC in C++20 mode it uncovered some issues of its own. Red Hat compiler engineer Jakub Jelinek noted on the GCC mailing list while providing patches to address C++20 build errors in GCC

Compiler engineer Marek Polacek of Red Hat recently proposed making the C++20 language specification (or rather the GNU++20 dialect) the default C++ version when not otherwise specified.

Polacek proposed declaring GCC's C++20 support no longer experimental and to use it as the default. The current default dialect is C++17 (GNU++17) that was set five years ago.

Qt Creator 18 adds experimental support for Development Containers and many more improvements.

Fil-C is a memory-safe implementation of C and C++ that aims to let C code — complete with pointer arithmetic, unions, and other features that are often cited as a problem for memory-safe languages — run safely, unmodified. Its dedication to being "fanatically compatible" makes it an attractive choice for retrofitting memory-safety into existing applications. Despite the project's relative youth and single active contributor, Fil-C is capable of compiling an entire memory-safe Linux user space (based on Linux From Scratch), albeit with some modifications to the more complex programs. It also features memory-safe signal handling and a concurrent garbage collector.

Qt 6.10 is now available, with new features and improvements for application developers and device creators!

Highlights for UI builders include a new flex-box layout system for Qt Quick, and support for more vector animations in SVG and Lottie format. And we have listened to your feedback and made it easier to exchange data between C++ code and a Qt Quick UI developed in QML. Such data can then be used with the new SearchField control, or with a new FilledSurface graph from the Qt Graphs module.

If you prefer to maintain your existing codebase, upgrading to Qt 6.10 ensures your application automatically aligns with high-contrast system settings on both desktop and mobile platforms. This and other improvements in our accessibility implementation directly benefits users reliant on assistive technologies, improving usability and inclusivity without requiring any additional development effort.

In addition to these highlights, new APIs across the Qt modules bring increased flexibility and productivity for both QML and C++ developers, and for users of Qt Widgets and Qt Quick.