An NB comment to fix an issue isn't something to worry about. It's not as if they're a score. It's a list of things someone things someone thinks that should be dealt with before release. Apply all P0 issues is probably going to be there, too. 

If we think this is P0, we should probably make that official. 

On Wed, Sep 7, 2022, 08:09 Thomas Köppe via Lib <lib@lists.isocpp.org> wrote:
On Wed, 7 Sept 2022, 12:54 Tim Song, <t.canens.cpp@gmail.com> wrote:

Ah, great! I'll bow out then, thank you!


On Wed, Sep 7, 2022 at 6:46 AM Thomas Köppe via Lib <lib@lists.isocpp.org> wrote:
OK, thanks! Who's going to file the issue? :-)

On Wed, 7 Sept 2022 at 12:28, Ville Voutilainen <ville.voutilainen@gmail.com> wrote:
On Wed, 7 Sept 2022 at 14:17, Thomas Köppe via SG10
<sg10@lists.isocpp.org> wrote:
>
> Aha, thanks -- yes, if the macros are normative, then it might indeed be best if we resolve this four-fold value bump collision with an LWG issue that captures the discussion.

They seem plenty normative to me, or that has least been the intent.
The standard requires the presence and values
of a set of macros, and they affect the meaning of portable programs
written against a particular standard.

Sure, the phrasing in [version.syn]/1, "The header <version> supplies
implementation-dependent information
about the C ++ standard library (e.g.,version number and release
date)." is a bit funny, because there shouldn't
be anything implementation-dependent about the macros and their
values. Luckily, "implementation-dependent"
is not a Term of Power. :)
_______________________________________________
Lib mailing list
Lib@lists.isocpp.org
Subscription: https://lists.isocpp.org/mailman/listinfo.cgi/lib
Link to this post: http://lists.isocpp.org/lib/2022/09/23610.php
_______________________________________________
Lib mailing list
Lib@lists.isocpp.org
Subscription: https://lists.isocpp.org/mailman/listinfo.cgi/lib
Link to this post: http://lists.isocpp.org/lib/2022/09/23612.php