News for hackers. Stuff that matters.
Re:C++26 Disapproved by account42 on Wednesday November 04, 2026 @04:21AM (#50363107)
The NBs should use this veto power more often until the committee learns to not push half-assed features into the standard. C++ is not a language that needs to "move fast and break things".
Re:C++26 Disapproved by locknitpicker on Wednesday November 04, 2026 @06:43AM (#50364270)
> The NBs should use this veto power more often until the committee learns to not push half-assed features into the standard.

This half-baked contracts proposal has been systematically cut out of the draft since at least 2020.

I mean, how long does it take to fix it? Perhaps it's unsalvageable?

Their proponents seem to be more interested in playing political games than to fix the mess they presented.

Re:C++26 Disapproved by jcranmer on Wednesday November 04, 2026 @09:29AM (#50366014)
I find it amusing that of all of the half-assed features in the standards, it's contracts that causes the vote to fail. I've seen firsthand how the standards committee just fundamentally disempowers anybody from actually objecting to a feature, and yet contracts is the one feature where all of those objections were heard at length, entertained repeatedly, and survived because the small coterie of a dozen or so people were unable to convince the other hundred people of their objections. The C++ committee process is deeply broken, and yet contracts is the one major feature where that process wasn't broken.
Re:C++26 Disapproved by rerdavies on Wednesday November 04, 2026 @01:24PM (#50369536)
[delayed]
Re:C++26 Disapproved by jcranmer on Wednesday November 04, 2026 @04:01PM (#50371468)
Given that all of the objections are explicitly over contracts, and only contracts, and not any of the other half-assed features in C++26, I don't think it's fair to say that that lesson isn't being drawn.