Ryan Liptak 68b87918df Fix handling of Windows (WTF-16) and WASI (UTF-8) paths ...

Windows paths now use WTF-16 <-> WTF-8 conversion everywhere, which is lossless. Previously, conversion of ill-formed UTF-16 paths would either fail or invoke illegal behavior.

WASI paths must be valid UTF-8, and the relevant function calls have been updated to handle the possibility of failure due to paths not being encoded/encodable as valid UTF-8.

Closes #18694
Closes #1774
Closes #2565

2024-02-24 14:05:24 -08:00

46 KiB

Raw Blame History

View Raw