Oops, I see I forgot to correct the date when I pasted the first line below.  This telecon will, of course, be held on July 28th as stated in the email subject.  If I ever come across a time machine, I suspect I'll find better uses for it than scheduling meetings in the past.

Also, I neglected to mention a LWG 3565 related email thread initiated by Peter last month; please also review https://lists.isocpp.org/sg16/2021/06/2444.php prior to the meeting (and my apologies again for the damaged archive encoding).


On 7/24/21 4:54 PM, Tom Honermann via SG16 wrote:

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

Our challenges finding consensus for various aspects of P2093 as discussed during our May 12th, May 26th, June 9th, and June 23rd telecons has me concerned about finding consensus for a resolution to LWG 3565.  Please re-read the P2093 related minutes and polls in those telecons prior to the meeting to refresh your memory of the encoding related concerns previously discussed and polled.  Any decision reached on LWG 3565 is likely to be adopted by implementors in their C++20 conforming modes, and may serve as a precedent for P2093 and other future papers, so it is important that we get this right.  Note that the proposed resolution does not address wide string support (e.g., whether transcoding is performed for std::format(L"День недели: {}", std::chrono::Monday)).  It would be useful for us to start discussion with a review of what current implementations actually do.

If we are fortunate enough to dispense with LWG 3565, we'll discuss P2348R0.  We have not previously discussed this paper, but we previously discussed the topic when discussing P2178R1 proposal 2 during our August 26th, 2020 telecon.  I don't anticipate the motivation for this paper being contentious, so please be prepared to discuss the proposed wording changes.