Title
Header for __cpp_lib_to_chars
Status
c++20
Section
[support.limits.general]
Submitter
S. B. Tam

Created on 2018-07-03.00:00:00 last changed 38 months ago

Messages

Date: 2018-11-12.04:39:29

Proposed resolution:

This wording is relative to (the Rapperswil post-mailing standard).

Change [support.limits.general] (Table 35) as indicated:

Macro nameValueHeader(s)
__cpp_lib_to_chars201611L<charconvutility>
Date: 2018-11-12.04:39:29

[ 2018-11, Adopted in San Diego ]

Date: 2018-07-20.00:00:00

[ 2018-07-20 Status to Tentatively Ready after five positive votes on the reflector. ]

Date: 2018-07-07.18:35:12

[ Marshall provides P/R and context ]

std::to_chars, etc were originally proposed for the header <utility> and SD-6 reflected that. Somewhere along the way, they was put into their own header <charconv>, but the document was never updated to reflect that.

When these macros were added to the standard, the (now incorrect) value was copied as well.

Date: 2018-07-03.00:00:00

After acceptance of P0941R2 into the working draft, in [support.limits.general], __cpp_lib_to_chars is required to be in <utility>. Since the relevant feature (std::to_chars and std::from_chars) is now in the header <charconv>, should the macro be defined in <charconv> instead of <utility>?

History
Date User Action Args
2021-02-25 10:48:01adminsetstatus: wp -> c++20
2018-11-12 04:39:29adminsetmessages: + msg10202
2018-11-12 04:39:29adminsetstatus: voting -> wp
2018-10-08 05:13:59adminsetstatus: ready -> voting
2018-07-20 21:06:57adminsetmessages: + msg10043
2018-07-20 21:06:57adminsetstatus: new -> ready
2018-07-07 18:35:12adminsetmessages: + msg10020
2018-07-07 18:35:12adminsetmessages: + msg10019
2018-07-03 00:00:00admincreate