I'd like to call attention to an editorial note present in the meeting
summary. Some of the discussion concerned how scanning of centered text
should work and questions were raised regarding how the Python parse
library handles this. I encourage the paper authors to consider if
std::scan() should adopt the behavior described below (presumably just
for format specifications that don't include an explicit field width)
and update the paper to provide rationale accordingly.

    [ /Editor's note:/ The "Format Specification" section in the Python
    parse project description <https://pypi.org/project/parse/> states:

> Note that the “center” alignment does not test to make sure
> the value is centered - it just strips leading and trailing
> whitespace.
>
    ]

Tom.

On 3/22/24 4:40 PM, Tom Honermann via SG16 wrote:
>
> The summary for the SG16 meeting held March 13th, 2024 is now
> available. For those that attended, please review and suggest
> corrections.
>
> * https://github.com/sg16-unicode/sg16-meetings#march-13th-2024
>
> Please note that SG16 will *_not_* meet on Wednesday of next week,
> March 27th, as had been originally scheduled. We'll resume meeting on
> April 10th.
>
> The following polls were taken:
>
> For P3154R0: Deprecating signed character types in iostreams
> <https://wg21.link/p3154r0>:
>
> *Poll 1: Recommend reserving |signed char| and |unsigned char| for use
> as integer types, not character types.*
>
> * Attendees: 11 (1 abstention)
> SF F N A SA
> 7 2 0 1 0
>
> * Consensus in favor.
>
> *Poll 2: Forward P3154R0 with the suggested modifications to the
> motivation section to LEWG for C++26.*
>
> * Attendees: 11 (3 abstentions)
> SF F N A SA
> 4 2 1 1 0
>
> * Consensus in favor.
>
> Tom.
>
>