Date: Sun, 30 Mar 2025 09:10:48 -0400
On Sunday, 30 March 2025 08:10:48 Eastern Daylight Time Jan Schultke via Std-
Proposals wrote:
> If we add overloads for std::print that work with char8_t, char16_t,
> and char32_t, then we may as well add the wchar_t overload. It's
> fundamentally the same problem.
I'd argue we should add char16_t first and foremost, then consider any of the
others. wchar_t should be either a compiler extension or a simple
reinterpret_cast of char16_t where the two are the same.
Proposals wrote:
> If we add overloads for std::print that work with char8_t, char16_t,
> and char32_t, then we may as well add the wchar_t overload. It's
> fundamentally the same problem.
I'd argue we should add char16_t first and foremost, then consider any of the
others. wchar_t should be either a compiler extension or a simple
reinterpret_cast of char16_t where the two are the same.
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Principal Engineer - Intel DCAI Platform & System Engineering
Received on 2025-03-30 13:10:50