Date: Mon, 28 Feb 2022 10:05:13 -0500
Our next meeting will be on Fri Mar 04, 2022 at 18:00 UTC
(https://www.timeanddate.com/worldclock/converter.html?iso=20220304T180000&p1=tz_pt&p2=tz_mt&p3=tz_ct&p4=tz_et&p5=1440).
You can join the meeting at https://iso.zoom.us/j/5513145100
**NEW PASSWORD: same as the old one, but spelled as a C reserved
identifier instead of a C++ keyword; contact Aaron Ballman if you have
questions **
We will be discussing the following papers:
P1774R5 (https://wg21.link/P2541R0) Consider renaming remove_quals
This is a rebuttal paper for WG14 N2927
(http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2927.htm) which was
adopted into C2x. It proposes renaming the accepted remove_quals
operator with a different spelling of unqual_typeof, but otherwise
keeps the same semantics.
P2215R1 (https://wg21.link/P2215R1) "Undefined behavior" and the
concurrency memory model
In relation to the "out of thin air" problems in SG1, this paper
discusses what undefined behavior means in the context of concurrent
threads. The paper provides a few possible interpretations. The author
is looking for feedback on the alternatives, especially as it relates
to interoperability between C and C++.
Thanks!
~Aaron
(https://www.timeanddate.com/worldclock/converter.html?iso=20220304T180000&p1=tz_pt&p2=tz_mt&p3=tz_ct&p4=tz_et&p5=1440).
You can join the meeting at https://iso.zoom.us/j/5513145100
**NEW PASSWORD: same as the old one, but spelled as a C reserved
identifier instead of a C++ keyword; contact Aaron Ballman if you have
questions **
We will be discussing the following papers:
P1774R5 (https://wg21.link/P2541R0) Consider renaming remove_quals
This is a rebuttal paper for WG14 N2927
(http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2927.htm) which was
adopted into C2x. It proposes renaming the accepted remove_quals
operator with a different spelling of unqual_typeof, but otherwise
keeps the same semantics.
P2215R1 (https://wg21.link/P2215R1) "Undefined behavior" and the
concurrency memory model
In relation to the "out of thin air" problems in SG1, this paper
discusses what undefined behavior means in the context of concurrent
threads. The paper provides a few possible interpretations. The author
is looking for feedback on the alternatives, especially as it relates
to interoperability between C and C++.
Thanks!
~Aaron
Received on 2022-02-28 15:05:27