No. Because people tend to make more mistakes if they try to use unsigned values in this manner in C/C++.

I’ve personally never encountered a bug that turned out to be caused by an unsigned value. YMMV, I guess.

If seen all sorts of bugs caused by surprise conversions, as well as overflows that cause bugs that would be statically detectable but can't become blocking errors because unsigned overflow is well defined.