You must log in or register to comment.
Still no contracts?
It would eliminate a billion bugs in all the code I’ve ever worked on. It’s sad.
Still no contracts?
In line with the release process for C++ standard specifications, where standards ship every 3 years but alternate between accepting new features and feature freeze releases, C++23 was the last release that was open to new features. This would mean C++26 is a feature freeze release following the new features introduced in C++23.
Contacts have been talked about since C++11 so it’s kinda sad that in 15 years they haven’t managed to get them done.
That’s perfectly fine. It’s a standardization process. Its goal is to set in stone a specification that everyone agrees to. Everything needs to line up.
In the meantime, some compiler vendors provide their own contracts support. If you feel this is a mandatory feature, nothing prevents you from using vendor-specific implementations. For example, GCC has support for contracts since at least 2022, and it’s mostly in line with the stuff discussed in the standardization meetings.
Huh? There is no such alternation between new features and feature freeze releases. In fact, C++26 will very likely get reflection as a major new feature. In comparison, the biggest core language feature in C++23 was probably “deducting this (explicit object member functions)”.
The only thing that keeps Contracts out of C++26 is that they might not be finished in time (they’ll need to be handed over from Evolution to Core by the February 2025 meeting, and then make it through Core review during the summer 2025 meeting).
Wake me when they add named arguments.
named arguments
Is this supposed to be a critical feature?
It’s about the only thing I miss when I use cpp. Makes code far more legible.
No mention of Reflection which was passed to the Core Working Group for wording review, or senders/receivers (on the library side) which was actually voted into the working paper.
