Tom Honermann via SG16:
> We now guarantee that char32_t character and string literals are UTF-32 encoded, but we don't have wording stating that char32_t
> objects always hold a Unicode code point value (though I would recommend against using them for other purposes).

Let's not do it. Can we go use string types like std::chrono? Using char32_t for code points or scalar values is too error prone
because char32_t lacks enforcement.