Date: Fri, 10 Jul 2026 05:25:16 -0700
On Fri, Jul 10, 2026 at 1:04 AM Guy Davidson <standard.guy_at_[hidden]>
wrote:
> It sounds to me like you are discussing part of the SG15 brief.
>
I guess I was too subtle (lol). I'll say it plainly: stakeholders can
charter a new Working Group under SC22. A sibling of WG21, not a study
group inside it. The sole product is a second library standard for C++,
with its own charter, its own convener, and its own tradeoffs on delivery
and ABI.
It sounds like the previous effort was competing for WG21's plenary time,
which is its own obstacle. That is evidence the committee is a
suboptimal venue,
not that the demand can't be served. And the delivery problem you describe
is solved the same way WG21 solves it: by specifying rather than shipping.
Nobody has done this because std:: absorbs the demand. Remove the
subsidized supplier and the formation pressure becomes real.
Well, that's my theory anyway :)
Best
wrote:
> It sounds to me like you are discussing part of the SG15 brief.
>
I guess I was too subtle (lol). I'll say it plainly: stakeholders can
charter a new Working Group under SC22. A sibling of WG21, not a study
group inside it. The sole product is a second library standard for C++,
with its own charter, its own convener, and its own tradeoffs on delivery
and ABI.
It sounds like the previous effort was competing for WG21's plenary time,
which is its own obstacle. That is evidence the committee is a
suboptimal venue,
not that the demand can't be served. And the delivery problem you describe
is solved the same way WG21 solves it: by specifying rather than shipping.
Nobody has done this because std:: absorbs the demand. Remove the
subsidized supplier and the formation pressure becomes real.
Well, that's my theory anyway :)
Best
Received on 2026-07-10 12:25:32
