7 ms·

> Ill-formed UTF-16 is replaced with U+FFFD by default, or escaped under {:?}. Silently corrupting the path seems an odd choice in this day and age, when WTF8

> Ill-formed UTF-16 is replaced with U+FFFD by default, or escaped under {:?}. Silently corrupting the path seems an odd choice in this day and age, when WTF8 has existed for many years and fixes this round trip bug / security vulnerability

silon42 3mo ago
Yes, but WTF-8 is not UTF-8.
- manwe150 3mo ago
  Yeah, but picking utf8 over wtf8 for this in 2026 feels a lot like picking utf16 over utf8 in 1995. You know the choice is broken and you know there is a correct fix already out there.