Date: Tue, 23 Aug 2022 12:57:56 -0400
This is your friendly reminder that this meeting is taking place tomorrow.
I neglected to mention previously; WG21 participation rules have changed
and SGs like SG16 have been impacted. Going forward, all attendees of
SG16 meetings are required to be at least one of:
1. A formal member of WG21; your name must appear in the ISO global
directory.
2. A formal member of one of the following liaison organizations:
1. JTC 1/SC 22/WG 14 (the C committee)
2. JTC 1/SC 22/WG 21 (the C++ committee)
3. ISO TC 37, Terminology and other language and content resources
4. JTC 1/SC 2, Coded character sets
5. JTC 1/SC 27, IT Security techniques
6. JTC 1/SC 41, Internet of things and digital twin
7. Ecma International
8. IEEE
9. Linux Foundation
10. MISRA
11. or any other recognized ISO liaison organization associated with
SC 22.
3. Invited by the convenor (one-time only; further participation will
require meeting one of the above two requirements).
If you wish to attend and do not qualify for one of the first two
requirements, please contact me and we'll get your participation sorted out.
Tom.
On 8/21/22 10:14 AM, Tom Honermann via SG16 wrote:
>
> SG16 will hold a telecon on Wednesday, August 24th, at 19:30 UTC
> (timezone conversion
> <https://www.timeanddate.com/worldclock/converter.html?iso=20220824T193000&p1=1440&p2=tz_pdt&p3=tz_mdt&p4=tz_cdt&p5=tz_edt&p6=tz_cest>).
>
> The agenda is:
>
> * Initial planning for Kona.
> * P2626R0: charN_t incremental adoption: Casting pointers of UTF
> character types <https://wg21.link/p2626r0>
>
> The next C++ committee meeting is scheduled for Kona from November 7th
> through the 12th <https://isocpp.org/files/papers/N4912.pdf>. There
> are likely to be NB comments for SG16 to respond to and we probably
> won't receive those comments with sufficient time to consider them and
> establish consensus positions before the start of the meeting. We'll
> therefore likely have to meet sometime during that week. I would like
> to get a sense of who all expects to attend the meeting in person for
> planning purposes. If few people plan to attend in person, then I
> probably won't request a room in Kona with the expectation that people
> that wish to attend from Kona participate via Zoom the same as other
> remote attendees.
>
> P2626R0 <https://wg21.link/p2626r0> is a new paper from Corentin that
> proposes new constexpr interfaces to perform an in-place replacement
> of an array of character type with an array of another character type
> where the two character types share an underlying type and where the
> elements of the replacement array retain the values of the prior
> array. The intent is to enable, for example, passing an array of
> char16_t type to a function that expects an array of wchar_t type
> without having to allocate new storage and/or copy the data. Please
> review the discussion from the email threads archived here
> <https://lists.isocpp.org/sg16/2022/08/3330.php> and here
> <https://lists.isocpp.org/sg16/2022/08/3335.php>. I expect more
> discussion to materialize on the SG16 mailing list in the next day or
> two, so please keep an eye out for new posts.
>
> Tom.
>
>
I neglected to mention previously; WG21 participation rules have changed
and SGs like SG16 have been impacted. Going forward, all attendees of
SG16 meetings are required to be at least one of:
1. A formal member of WG21; your name must appear in the ISO global
directory.
2. A formal member of one of the following liaison organizations:
1. JTC 1/SC 22/WG 14 (the C committee)
2. JTC 1/SC 22/WG 21 (the C++ committee)
3. ISO TC 37, Terminology and other language and content resources
4. JTC 1/SC 2, Coded character sets
5. JTC 1/SC 27, IT Security techniques
6. JTC 1/SC 41, Internet of things and digital twin
7. Ecma International
8. IEEE
9. Linux Foundation
10. MISRA
11. or any other recognized ISO liaison organization associated with
SC 22.
3. Invited by the convenor (one-time only; further participation will
require meeting one of the above two requirements).
If you wish to attend and do not qualify for one of the first two
requirements, please contact me and we'll get your participation sorted out.
Tom.
On 8/21/22 10:14 AM, Tom Honermann via SG16 wrote:
>
> SG16 will hold a telecon on Wednesday, August 24th, at 19:30 UTC
> (timezone conversion
> <https://www.timeanddate.com/worldclock/converter.html?iso=20220824T193000&p1=1440&p2=tz_pdt&p3=tz_mdt&p4=tz_cdt&p5=tz_edt&p6=tz_cest>).
>
> The agenda is:
>
> * Initial planning for Kona.
> * P2626R0: charN_t incremental adoption: Casting pointers of UTF
> character types <https://wg21.link/p2626r0>
>
> The next C++ committee meeting is scheduled for Kona from November 7th
> through the 12th <https://isocpp.org/files/papers/N4912.pdf>. There
> are likely to be NB comments for SG16 to respond to and we probably
> won't receive those comments with sufficient time to consider them and
> establish consensus positions before the start of the meeting. We'll
> therefore likely have to meet sometime during that week. I would like
> to get a sense of who all expects to attend the meeting in person for
> planning purposes. If few people plan to attend in person, then I
> probably won't request a room in Kona with the expectation that people
> that wish to attend from Kona participate via Zoom the same as other
> remote attendees.
>
> P2626R0 <https://wg21.link/p2626r0> is a new paper from Corentin that
> proposes new constexpr interfaces to perform an in-place replacement
> of an array of character type with an array of another character type
> where the two character types share an underlying type and where the
> elements of the replacement array retain the values of the prior
> array. The intent is to enable, for example, passing an array of
> char16_t type to a function that expects an array of wchar_t type
> without having to allocate new storage and/or copy the data. Please
> review the discussion from the email threads archived here
> <https://lists.isocpp.org/sg16/2022/08/3330.php> and here
> <https://lists.isocpp.org/sg16/2022/08/3335.php>. I expect more
> discussion to materialize on the SG16 mailing list in the next day or
> two, so please keep an eye out for new posts.
>
> Tom.
>
>
Received on 2022-08-23 16:57:59