Date: Wed, 22 Sep 2021 23:22:57 +0200
On Behalf of Aaron, Here is the agenda of the next SG22 meeting (Fri Oct 1,
2021)
Thanks :)
---------- Forwarded message ---------
From: Aaron Ballman via Liaison <liaison_at_[hidden]>
Date: Tue, Sep 21, 2021 at 8:46 PM
Subject: [wg14/wg21 liaison] C and C++ Compatibility Oct Agenda
To: WG14/WG21 liaison mailing list <liaison_at_[hidden]>
Cc: Aaron Ballman <compatibility.sg.chair_at_[hidden]>
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/09/0752.php
2021)
Thanks :)
---------- Forwarded message ---------
From: Aaron Ballman via Liaison <liaison_at_[hidden]>
Date: Tue, Sep 21, 2021 at 8:46 PM
Subject: [wg14/wg21 liaison] C and C++ Compatibility Oct Agenda
To: WG14/WG21 liaison mailing list <liaison_at_[hidden]>
Cc: Aaron Ballman <compatibility.sg.chair_at_[hidden]>
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/09/0752.php
Received on 2021-09-22 16:23:10