Hacker News
points by account42 4 days ago | 0 comments
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".
[–] locknitpicker 4 days ago
> 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. Apparently they don't mind sabotaging the C++ standardization process to get their way.

[–] jcranmer 4 days ago
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.
[–] rerdavies 3 days ago
Is it unreasonable to draw a lesson from previous half-assed features that failed after ratification, and say enough is enough?
[–] jcranmer 3 days ago
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.