Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.
 help



Is it unreasonable to draw a lesson from previous half-assed features that failed after ratification, and say enough is enough?

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.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: