Some questions about wil::reg about wil HOT 3 OPEN

Regarding your first question:

• Not all consumers of WIL have access to the STL, so any code that uses STL types must be guarded, limiting their usefulness. This has a cascading effect where any functions using those functions must also be guarded
• For input, none of the Windows APIs accept std::basic_string, so using that for input params would needlessly require consumers to construct one, wasting time and memory
• For output, std::basic_string is a terrible API to use for output buffers due to the lack of some form of uninitialized_resize that would allow us to change the underlying buffer size without needlessly writing zeros to the soon-to-be overwritten or discarded memory

from wil.

due to the lack of some form of uninitialized_resize

For the sake of completion: C++23 has introduced resize_and_overwrite, although this doesn't help with older C++ standards of course.

from wil.

Huh, good to know, I missed that. But yeah, the C++ version requirement (the Windows codebase is still on C++17 as the default AFAIK) and all other issues still apply.

from wil.