Created on 2018-07-03.00:00:00 last changed 45 months ago
Proposed resolution:
This wording is relative to (the Rapperswil post-mailing standard).
Change [support.limits.general] (Table 35) as indicated:
Macro name | Value | Header(s) |
---|---|---|
__cpp_lib_to_chars | 201611L | <charconv |
[ 2018-11, Adopted in San Diego ]
[ 2018-07-20 Status to Tentatively Ready after five positive votes on the reflector. ]
[ 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.
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:01 | admin | set | status: wp -> c++20 |
2018-11-12 04:39:29 | admin | set | messages: + msg10202 |
2018-11-12 04:39:29 | admin | set | status: voting -> wp |
2018-10-08 05:13:59 | admin | set | status: ready -> voting |
2018-07-20 21:06:57 | admin | set | messages: + msg10043 |
2018-07-20 21:06:57 | admin | set | status: new -> ready |
2018-07-07 18:35:12 | admin | set | messages: + msg10020 |
2018-07-07 18:35:12 | admin | set | messages: + msg10019 |
2018-07-03 00:00:00 | admin | create |