[Cfp-interest 3289] N3288 (Give consistent wording for SNAN initialization)

[RAJAN BHAKTA]

Hello,

Summary for this morning:
N3286 Floating-point exceptions for macro replacements:
  Straw poll: Adopt N3286 in C2Y?
    10+6/0/6. 16/0/6. Passes.
  ^AI: Ballman: Put N3286 to the list of retroactive changes to previous standards.

N3287 Nonsensical Parenthetical:
  Straw poll: Put N3287 in C2Y?
    10+8/0/4. 18/0/4. Passes.

N3288 Give consistent wording for SNAN initialization
  Request to have N3288 say translation time instead of static storage duration.

With regards to the last item, here is a proposed update. Please let me know if you have any issues with it:

Proposal for C2Y
WG14 Nxxxx (revision 2 of N3288)
Title: Give consistent wording for SNAN initialization
Author, affiliation: C FP group
Date: 2024-09-30
Proposal category: Editorial
Reference: Base document: N3220

Changes from N3288 (1st version):
  - As per WG14 preference (to include constexpr), the "translation time" wording is selected instead.

Proposal:

SNAN used at translation time has different wording in two places: 5.2.4.2.2#22 mentions SNAN for translation time initializer, while H.3#6 mentions static or thread storage duration. There should be consistent wording in both places. In the following, "translation time" phrase is used to maintain consistency. In addition, binding of the "optional unary + or - operator" phrase may be confusing so it is moved to make it more clear that you can have +, -, or no preceding operator for a signaling NaN macro.

Proposed changes:

Change H.3#6 (in N3220) from:

If an optional unary + or - operator followed by a signaling NaN macro is used for initializing an object of the same type that has static or thread storage duration, the object is initialized with a signaling NaN value.

To:

If a signaling NaN macro, optionally preceded by the unary + or – operator, is used for initializing an object of the same type that is evaluated at translation time, the object is initialized with a signaling NaN value.

Change 5.2.5.3.2#28 (in N3220) from:

If an optional unary + or - operator followed by a signaling NaN macro is used as an initializer that is evaluated at translation time, the object is initialized with a signaling NaN value.

To:

If a signaling NaN macro, optionally preceded by the unary + or – operator, is used for initializing an object of the same type that is evaluated at translation time, the object is initialized with a signaling NaN value.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.oakapple.net/pipermail/cfp-interest/attachments/20240930/fa8f2f8e/attachment.htm>