Windows builds are incredibly noisy about libuv HOT 2 CLOSED

if you were interested in getting these silenced yourself

On a case-by-case basis yes, in general no.

The "potentially uninitialized local variable" warnings are probably false positives but it'd be good to check them anyway.

A lot of the other warnings however are bogus and I plan to encumber the code with things like pointless casts in order to pacify a compiler. To pick two examples from src/idna.c:

C:\Users\gocdu\programs\libuv\src\idna.c(80): warning C4245: 'return': conversion from 'int' to 'unsigned int', signed/unsigned mismatch

That's the perfectly legal and well-defined idiom of return -1 in a function that returns unsigned int.

Now, you could change that to return ~0u but that's definitely less robust. It quietly starts doing the wrong thing when the return type is changed to e.g. unsigned long (because then it needs to be return ~0ul)

C:\Users\gocdu\programs\libuv\src\idna.c(500): warning C4244: '=': conversion from 'int32_t' to 'char', possible loss of data

Libuv literally checks on the previous line that the value is in range but the compiler isn't smart enough to realize that.

from libuv.

Yes, I understand. Thank you for your time.

from libuv.