It causes such issues as opening of files by filename not being cross platform with standard libc functions since in Windows w-string versions are required since UTF-16 chars can have 0-bytes that aren't zero terminators
It makes sense because UTF-16 is a sequence of uint16_t values, so both bytes must be zero, not just one.
It makes sense because UTF-16 is a sequence of uint16_t values, so both bytes must be zero, not just one.