Reminder that this telecon will be taking place tomorrow.

Please review the summary from our last telecon.

With regard to C++23 goals and priorities, what I plan to do is to briefly review suggestions for things we could work on (including items listed below, others already discussed in email, and any suggestions offered during the meeting).  An item that is nominated for prioritization by someone present and for which a champion willing to progress it is identified will become a candidate for prioritization polling.  I expect this will yield ~12 candidates.  We'll then poll those with the expectation of identifying up to six items to prioritize with good consensus.  To poll, everyone will get 4 votes (maybe more, maybe less, depending on the item count) to cast for their top 4 candidates.  If anyone has concerns about this, please feel free to express them and suggest an alternative method.

The WG14 related items that we are tracking (listed earlier in this email thread) will not be included in the polling above.  That is only because I don't anticipate spending SG16 time on them; champions are encouraged to progress them through SG22 and WG14 channels.

Here is an updated list of items to consider.
Tom.

On 3/16/21 10:59 AM, Tom Honermann via SG16 wrote:

SG16 will hold a telecon on Wednesday, March 24th at 19:30 UTC (timezone conversion).

For participants in North America, please note that daylight savings time went into effect this past weekend, so this telecon will start one hour later than our last telecon (Mexico doesn't observe DST until April 4th).

The agenda is:

For D2314R1 and D2297R1, discussion will be limited to new information that might help to break the stalemate regarding use of an abstract character set or UCS scalar values as the specification tool for describing translation.  If consensus is not reached, we'll poll forwarding D2314R1 with direction that EWG and/or CWG choose the wording mechanism.

Per P1000, papers targeting C++23 must be forwarded by EWG/LEWG to CWG/LWG by the February, 2022 meeting (Portland).  However, the deadline for initial papers proposing new language features is ~November, 2021.  Time is running short, and competition for time in EWG/LEWG will increase.

The following lists the current state of SG16 related papers and our C++23 effort to date.  This is presented as food for thought.  What story does this tell?  How will that story be received by the C++ community?  What should we do with our remaining time to either strengthen or change that story?  What can we realistically do to bring more direct benefits to the C++ community?  It may be interesting to review what we were thinking about during our March 13th, 2019 telecon.

These papers have been accepted for C++23:

These papers have been approved by EWG and are in the pipeline for CWG:

These papers have been approved by SG16 and are in the pipeline for EWG/LEWG:

These papers are in the pipeline for EWG/LEWG, but require a revision to make progress:

These papers are currently active in SG16:

With that summary of what we have been doing above in mind, the following lists provide some options for what we could work on next.

These are existing papers available for SG16 to prioritize: (Some of these, such as P1629, are awaiting revisions).

And finally, here are some ideas that have been discussed, but that we do not currently have papers covering:

Our efforts will need to be balanced with any effort expended to align C23 with changes made for C++20 and C++23:

Tom.