C++ Logo


Advanced search

Re: Agenda for the 2022-04-13 SG16 telecon

From: Charlie Barto <Charles.Barto_at_[hidden]>
Date: Wed, 13 Apr 2022 19:06:32 +0000
We fixed that stack overflow, by the way, but I think we could still be better about diagnosing the issue, we parse the first value as a type specifier (because the type is "whatever is left over" and the long fills cause the first part of the format specifier to not parse as "fill+align"), so you either get "invalid type specifier" or "expected a }" depending on if the first code-unit (in practice type specifiers are all one code-unit long) is a valid type specifier for the argument.

-----Original Message-----
From: SG16 <sg16-bounces_at_[hidden]> On Behalf Of Tom Honermann via SG16
Sent: Wednesday, April 13, 2022 11:01 AM
To: Daniel Krügler <daniel.kruegler_at_[hidden]>
Cc: Tom Honermann <tom_at_[hidden]>; SG16 <sg16_at_[hidden]>
Subject: Re: [SG16] Agenda for the 2022-04-13 SG16 telecon

On 4/13/22 11:48 AM, Daniel Krügler wrote:
> Am Mi., 13. Apr. 2022 um 17:34 Uhr schrieb Tom Honermann <tom_at_[hidden]>:
>> On 4/12/22 1:51 PM, Daniel Krügler wrote:
>>> Am Di., 12. Apr. 2022 um 19:35 Uhr schrieb Tom Honermann via SG16
>>> <sg16_at_[hidden]>:
>>>> This is your friendly reminder that this telecon is taking place tomorrow.
>>>> A draft of D2572R0 (std::format() fill character allowances) is now available at https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Ftahonermann%2Fstd-proposals%2Fmaster%2Fd2572r0.html&amp;data=05%7C01%7CCharles.Barto%40microsoft.com%7C5e2410da56bc438b627008da1d778c2a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637854696563495558%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=YrJ57rl4a7jX2UCcAtyikBp9QV%2FxfhRymfkJECnIqwM%3D&amp;reserved=0. It still needs some polishing and I need to work on the wording, but I think it will suffice to confirm direction tomorrow (we won't poll to forward it).
>>> 1) For the wording change in [format.string.std] p1 an insertion
>>> marker is missing around "U+007B LEFT CURLY BRACKET"
>> Thank you, fixed!
>> (The marker wasn't actually missing; apparently I was trying to
>> declare an int rather than insert markup!)
>>> 2) [format.string.std] p2 new inserted sentence: Shouldn't "fill" be
>>> in italics for the first occurrence of "fill specifier"?
>> Yes, I think so, thank you, fixed.
>> Should just the first occurrence be in italics? I admit, I've had a
>> hard time understanding when italics should and should not be used.
>> In this case, "fill" is referring to a grammar term and I thought all
>> such references should be italicized (there is also a reference in
>> the following note that I had already put in italics).
> Yes, all references to grammar terms should use italics.

Thank you for confirming; the second occurrence is now in italics as well.


> - Daniel
SG16 mailing list

Received on 2022-04-13 19:06:36