Niall Douglas:
> We are getting within a cat's whisker of UTF-8 being the default narrow
> encoding on Windows for new Visual Studio projects i.e. all the ANSI and
> char APIs on Windows would default to speaking UTF-8 in new or upgraded
> code. What you propose would ruin that effort.
>
> You may not be aware, but after a discussion with some Microsoft folk, I
> went ahead and submitted that as a feature request for the next major
> release of Visual Studio. And from what I am told, they are seriously
> considering it. The Windows console supports it, Windows supports it,
> the MSVCRT runtime supports it when asked. All someone needs to do is
> flip the switch for new projects targeting latest Windows 10 only, and
> we've done it.
>
> Having char = utf8 across all the major platforms would be an *enormous*
> win. Please aid that effort.

Sure, but I think C++20 projects should not use char unless in the
lowest levels when talking to OS.