You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Contrary to what is stated in the docs, source code does no seem to have support for utf16 an utf32 char sequences. At least specialization of path_traits for is_pathable is missing and I assume for convert as well. I am not sure, what the internal decisions are, maybe its just postponed?
The text was updated successfully, but these errors were encountered:
Could the documentation be updated to reflect that? Right now, it contains references to char16_t, char32_t, u16string and u32string in various places:
Contrary to what is stated in the docs, source code does no seem to have support for utf16 an utf32 char sequences. At least specialization of path_traits for is_pathable is missing and I assume for convert as well. I am not sure, what the internal decisions are, maybe its just postponed?
The text was updated successfully, but these errors were encountered: