Date: Mon, 13 Jul 2026 10:39:45 -0700
On Mon, Jul 13, 2026 at 9:10 AM Jens Maurer <jens.maurer_at_[hidden]> wrote:
> Personally, I don't think spreading C++ library review bandwidth across more
> than one SC22 Working Group gets us the best outcome.
>
I agree. But I am envisioning something different. What I would like to
see, is a separate working group staffed by different people. A different
convener. Different set of experts. Perhaps from the companies who are
direct stakeholders in "std/std2 as package manager."
They do their own thing. If they want std2::vector<tribool>? They get it.
They want std2::movie_player? Sure!
It keeps it away from us. The libraries that we would reject, they can
have, and it does not affect our bandwidth at all.
Instead, it gives LEWG a lever. They can say: "This looks like a good
library proposal for WG{Other}." The result is fewer library proposals, and
the ones we let in are of higher quality since they are filtered. I think
this something people want.
Best
> Personally, I don't think spreading C++ library review bandwidth across more
> than one SC22 Working Group gets us the best outcome.
>
I agree. But I am envisioning something different. What I would like to
see, is a separate working group staffed by different people. A different
convener. Different set of experts. Perhaps from the companies who are
direct stakeholders in "std/std2 as package manager."
They do their own thing. If they want std2::vector<tribool>? They get it.
They want std2::movie_player? Sure!
It keeps it away from us. The libraries that we would reject, they can
have, and it does not affect our bandwidth at all.
Instead, it gives LEWG a lever. They can say: "This looks like a good
library proposal for WG{Other}." The result is fewer library proposals, and
the ones we let in are of higher quality since they are filtered. I think
this something people want.
Best
Received on 2026-07-13 17:39:58
