It also blocks later adoption of a contract feature that would make C++ better.
SD-4: "
Delay vs. bird in the hand. We cannot act on ideas without papers, and we do not significantly delay progress on concrete proposals in order to wait for alternative proposals we might get in the future. [...]"
What is the paper number of the proposal of the contract feature which the C++26 CD is blocking later adoption of?
We have from time to time removed features from the WP, or in some cases from the IS.
In none of those cases did we have a replacement to put in its place.
And in some cases, competing proposals never materialize, which is what lead to SD-4.
If it turns out to be the case that we decide to remove contracts, it will take significant time and effort to come up with a replacement.
So far, I haven't seen any new technical information (but it could be lost in the flood of papers and emails). And it isn't like one hasn't had years to come up with a competing proposal, the deployment experience for it some have claimed is part of the minimum, etc.
--