[libc-commits] [libc] [libc] Add UTF-16 support in CharacterConverter [1/6] (PR #230434)

[Alex Strelnikov via libc-commits]

strel-12 wrote:

> I think I'm willing to accept either. I defer to you two discussing which option to use.

I considered it some more and would prefer the addition of the `enum` on `mbstate`. @michaelrj-google WDYT?

> Though I still think we should check for overlong encoding / out-of-range code points. The former causes the transformation to be non-bijective and has caused security problems historically. The later cannot be encoded by UTF-16.

I am not opposed to the check, but I think it would be good to modify the UTF-8 path in its own PR.



https://github.com/llvm/llvm-project/pull/230434