tahonermann
commented
3 months ago SG16 discussed this issue during its 2024-02-21 meeting. The following polls were taken:
- Poll 2: Approve the LWG 4044 proposed resolution with the wording about diagnosing invalid code units removed.
- Attendees: 9
- No objection to unanimous consent.
SG16 favors removing the following text (both occurrences) from the proposed wording. This is motivated by a lack of understanding regarding what it means to diagnose such invalid code unit sequences given that the input is likely provided at run-time.
If invoking the native Unicode API does not require transcoding, implementations are encouraged to diagnose invalid code units.
Some concern was expressed regarding how the current wording is structured. At present, the wording leads with a Windows centric perspective; if the stream refers to a terminal ... use the native Unicode API ... otherwise write code units to the stream. It might be an improvement to structure the wording such that use of the native Unicode API is presented as a fallback for implementations that require its use when writing directly to the stream is not sufficient to produce desired results. In other words, the wording should permit direct writing to the stream even when the stream is directed to a terminal and a native Unicode API is available when the implementation has reason to believe that doing so will produce the correct results. For example, Microsoft's HoloLens has a Windows based operating system, but it only supports use of UTF-8 as the system code page and therefore would not require the native Unicode API bypass; implementations for it could avoid the overhead of checking to see if the stream is directed to a console.
SG16 review is complete and this now rests solely in LWG's capable hands.
https://cplusplus.github.io/LWG/issue4044