Date: Thu, 23 Oct 2025 14:19:55 -0500
On Tue, Oct 21, 2025 at 12:09 PM John Spicer via SG15 <sg15_at_[hidden]>
wrote:
> It also blocks later adoption of a contract feature that would make C++
> better.
>
SD-4 <https://wg21.link/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.
wrote:
> It also blocks later adoption of a contract feature that would make C++
> better.
>
SD-4 <https://wg21.link/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.
-- Nevin ":-)" Liber <mailto:nevin_at_[hidden] <nevin_at_[hidden]>> +1-312-623-5420
Received on 2025-10-23 19:20:38
