Thanks for the reminder
Here is an updated draft of P2361
https://isocpp.org/files/papers/D2361R3.pdf

Corentin

On Fri, Oct 1, 2021 at 1:17 PM Aaron Ballman via Liaison <
liaison_at_[hidden]> wrote:

> Reminder: there will be an SG22 telecon today in just under six hours
> (at 17:00 UTC
>
> https://www.timeanddate.com/worldclock/converter.html?iso=20211001T170000&p1=tz_pt&p2=tz_mt&p3=tz_ct&p4=tz_et&p5=1440&p6=tz_cest
> ).
> Please see the agenda below for details.
>
> Hope to see you there!
>
> ~Aaron
>
> On Tue, Sep 21, 2021 at 2:45 PM Aaron Ballman
> <compatibility.sg.chair_at_[hidden]> wrote:
> >
> > Our next meeting will be on Fri Oct 1, 2021 at 17:00 UTC
> > (
> https://www.timeanddate.com/worldclock/converter.html?iso=20211001T170000&p1=tz_pt&p2=tz_mt&p3=tz_ct&p4=tz_et&p5=1440&p6=tz_cest
> ).
> >
> > You can join the meeting at https://iso.zoom.us/j/5513145100 with the
> > same password used as last time; please email me if you need the
> > password.
> >
> > We will be discussing the following papers:
> >
> > WG14 N2757/P2390R1 (https://wg21.link/P2390R1) Add annotations for
> > unreachable control flow
> > P0627R5 (https://wg21.link/P0627R5) Function to mark unreachable code
> > This is joint discussion of both the WG14 and WG21 proposals which
> > propose adding a facility for marking that an expression is expected to
> > be unreachable. The authors are primarily looking for design feedback.
> >
> > P2361R2 (http://wg21.link/P2361R2) Unevaluated string literals
> > C and C++ have the notion of source and execution character sets, but
> > have some string literals that are evaluated in neither, such as
> > string literals used to emit diagnostics or within _Pragma. This paper
> > proposes unevaluated string literals as a new kind of string literal
> > for these purposes. The authors are primarily looking for design
> > feedback.
> >
> > P2362R3 (https://wg21.link/P2362R3) Remove non-encodable wide
> > character literals and multicharacter wide character literals
> > Proposes adding restrictions to wide character literals so that use of
> > unencodable characters or multiple characters in wide character
> > literals is ill-formed. The authors do not anticipate this will break
> > user code, but are looking for feedback on issues with the proposal
> > for either users or implementers.
> >
> > Thanks!
> >
> > ~Aaron
> _______________________________________________
> Liaison mailing list
> Liaison_at_[hidden]
> Subscription: https://lists.isocpp.org/mailman/listinfo.cgi/liaison
> Link to this post: http://lists.isocpp.org/liaison/2021/10/0838.php
>