bugprone-signed-char-misuse check is currently limited to assignments and variable declarations where a signed char is assigned to an integer variable.
The header declares character-handling functions (isdigit, isspace, toupper, etc.) that operate on an int argument.
In all the cases the argument value should be representable as an unsigned char or should equal to EOF. It is an undefined behavior If the argument has any other value.
It would be very helpful if bugprone-signed-char-misuse check reported the above-mentioned cases as well.
llvmbot
commented
1 year ago
bugprone-signed-char-misuse check is currently limited to assignments and variable declarations where a signed char is assigned to an integer variable.
The header declares character-handling functions (isdigit, isspace, toupper, etc.) that operate on an int argument.
In all the cases the argument value should be representable as an unsigned char or should equal to EOF. It is an undefined behavior If the argument has any other value.
It would be very helpful if bugprone-signed-char-misuse check reported the above-mentioned cases as well.