> I also, on reflection, think excluding char and wchar is misguided. The
> contract is that char8 etc are utf-8 etc, but it's also frequently the case
> that the execution narrow and wide encodings are also unicode. That you
> have possible GIGO errors isn't a good reason to block possible correct
> use. It just encourages casting.

We could use concepts to check later, Just need to define proper
concepts which I don't have yet in my design. But I'd say using strong
types still feels better.