> In this case its extra-awkward to have an attempt of having unicode support on a function that takes a single char as an input Nitpick: it doesn’t take a cha

> In this case its extra-awkward to have an attempt of having unicode support on a function that takes a single char as an input Nitpick: it doesn’t take a char; it takes an int that must either be representable as unsigned char or be equal to EOF (https://en.cppreference.com/w/c/string/byte/isspace https://en.cppreference.com/w/c/string/byte/isspace) Given that description, I don’t think anybody attempted to have unicode support for isspace. IMO, the bug is to call isspace for bytes extracted from utf-8 data.