C++ Logo


Advanced search

Re: nullptr_t and nullopt_t should both have operator<=> and operator== to enable the *_with concepts

From: Arthur O'Dwyer <arthur.j.odwyer_at_[hidden]>
Date: Fri, 9 Jul 2021 09:32:55 -0400
On Fri, Jul 9, 2021 at 7:18 AM Giuseppe D'Angelo via Std-Proposals <
std-proposals_at_[hidden]> wrote:

> Il 09/07/21 08:49, Justin Bassett ha scritto:
> > Thanks for the insight. I don't know much about the different working
> > groups. What are the different groups, and what does it mean if I target
> > them (other than putting them under "Audience")? How do I know which
> > groups to target?
> Please see here:
> https://isocpp.org/std/the-committee
> I'm far from an expert in the area, but you're proposing design changes
> to both language and library, so you should target the respective
> Evolution groups, and possibly their Incubators study groups.

I'm also not an expert. :) My understanding is that for the purposes of
the "Audience" field, literally all you have to do is categorize your paper
as one of three kinds: "CWG," "LWG," or both. Once you've marked your paper
appropriately as "CWG" and/or "LWG", then that specific paper's progress
through the EWGI->EWG->CWG and/or LEWGI/LEWG/LWG funnels will be tracked in
real time by

As far as I know, marking your paper as "Audience: CWG" will not magically
skip it to the front of the CWG queue; and marking it "Audience: EWGI" will
not hinder its progress through EWG (except perhaps to waste a microsecond
of Hal's time in categorizing it). But if your paper proposes a
*core-language* change, and you mark it "Audience: *LWG*" as if it were a
library-only paper, then you might waste an hour of someone(s)'s time.


Received on 2021-07-09 08:33:09