Reminder! Our next meeting will be on Fri Jul 9, 2021 at 17:00 UTC
(https://www.timeanddate.com/worldclock/converter.html?iso=20210709T170000&p1=tz_pt&p2=tz_mt&p3=tz_ct&p4=tz_et&p5=1440&p6=tz_cest).

Note, this meeting is one week later than typical due to potential
conflicts with folks taking a long weekend for the Jul 4 US holiday.
See below for the July agenda.

Hope to see you all next Friday!

~Aaron

On Mon, Jun 21, 2021 at 11:46 AM Aaron Ballman
<compatibility.sg.chair_at_[hidden]> wrote:
>
> Our next meeting will be on Fri Jul 9, 2021 at 17:00 UTC
> (https://www.timeanddate.com/worldclock/converter.html?iso=20210709T170000&p1=tz_pt&p2=tz_mt&p3=tz_ct&p4=tz_et&p5=1440&p6=tz_cest).
>
> Note, this meeting is one week later than typical due to potential
> conflicts with folks taking a long weekend for the Jul 4 US holiday.
>
> You can join the meeting at https://iso.zoom.us/j/5513145100 with the
> same password used as last time.
>
> We will be discussing the following papers:
>
> P2290R0 (https://wg21.link/p2290r0) Delimited escape sequences
> Proposes new syntax for specifying escape sequences in a way that
> explicitly delimits what is part of the escape sequence and what is
> not. The paper targets C++ but is of interest in C due to the shared
> syntax for these escape sequences.
>
> P2316R0 (https://wg21.link/p2316r0) Consistent character literal encoding
> Proposes making character literals in the preprocessor have the same
> semantics as character literals during source translation. The
> proposal wishes to standardizing existing practice in common C and C++
> implementations by using the same character encodings in both phase 4
> and 7 of translation.
>
> P2295R3 (https://wg21.link/p2295r3) Support for UTF-8 as a portable
> source file encoding
> This paper proposes requiring implementations to support UTF-8 as a
> source code file encoding in addition to whatever
> implementation-defined file encodings they currently support.
>
> Thanks!
>
> ~Aaron