Improvements to Std:Format in C++26

Discussion (7 Comments)Read Original on HackerNews

Longhanks•about 2 hours ago

> A related issue solved along was Windows string representation of paths. std::filesystem::path stores its text in wchar_t encoded as UTF-16 (Windows native). But p.string() narrows it down to the active code page, rather than UTF-8 which is what the formatting library expects. The result was a non-ASCII path could get transcoded to gibberish. The C++26 std::formatter<std::filesystem::path> converts Windows native UTC-16 to UTF-8 using Unicode transcoding and avoiding code pages, therefore solving the problem.

...only to then convert it back to UTF-16 for WriteConsoleW(), which std::print() usually calls (unless not running in a console) (https://github.com/microsoft/STL/blob/488e7953685722d2d6666f...).

veltas•about 3 hours ago

Surely std::print() shouldn't print anything?

CamouflagedKiwi•about 2 hours ago

It's a typo, he describes it as std::println in the text, but the code snippet is just print()

steeleduncan•about 3 hours ago

I think it is a typo, and should be std::println()

nikbackm•about 3 hours ago

Why even call it in that case?

xuhu•about 3 hours ago

It's apparently a typo in the article, they probably meant to write `println()`.

IshKebab•about 1 hour ago

Typo in this case, but in general supporting "useless" code like this is sometimes a good idea because it makes writing generic code easier. Maybe not in this case.

Improvements to Std:Format in C++26

⚡ Community Insights

Discussion (7 Comments)Read Original on HackerNews