This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of Resolved status.
Section: 30.3.1.3 [locale.cons] Status: Resolved Submitter: Hubert Tong Opened: 2022-02-14 Last modified: 2023-03-22
Priority: 3
View all other issues in [locale.cons].
View all issues with Resolved status.
Discussion:
For
locale(const locale& other, const locale& one, category cats);
the Remarks say:
The resulting locale has a name if and only if the first two arguments have names.
The case where cats is locale::none seems very similar to the issue that LWG 2295 reports with the case where the provided facet pointer is nullptr. That is, if no composition is actually occurring, then using the name of other seems to be reasonable.
It would help consistency if both cases are treated the same way. Note: The locale::all case should not imply using the name of one. locale::all does not necessarily cover all of the C locale categories on a platform.[2022-03-04; Reflector poll]
Set priority to 3 after reflector poll.
[2022-11-01; Jonathan comments]
The proposed resolution of 2295 would resolve this too.
[2023-03-22 LWG 2295 was approved in Issaquah. Status changed: New → Resolved.]
Proposed resolution: